Live data from Hacker News

Ask HN: What's your go-to back end for simple projects?

news.ycombinator.com

41–50 of 65 posts

Re: Ask HN: What's your go-to back end for simple projects?

#41
post #18

Flask! It's Pythonic and good. Once you've done a couple of Flask projects, you can spin up a new microservice in a couple of hours. It's much lighter weight than Django, so it forces you to keep fewer moving parts in your head while hacking. http://flask.pocoo.org/ Lately, I've been using Flask on the back-end, and React on the front-end.

Hi Everyone. I'm actually working on a "starter" project that only focuses on the backend. It uses Flask and PostgresQL and includes fabric deployment scripts to get the app running on Debian. Please check it out and let me know what you think

https://github.com/johnwheeler/mvp-starter

Re: Ask HN: What's your go-to back end for simple projects?

#43
post #28

I guess I'm old school. For simple projects I still use Perl with CGI.pm and a flat file database that stores data in CGI.pm's "name=value" format in a text file. If I need templates I'll add "HTML:Template", for email I'll add "Mail::Sendmail", et cetera, to my perl cgi script.

I'm old school as well, last time I had a "simple" project that didn't allow setting up a SQL RDMS I used flat files, and for system administration by users their presence in various directories and Windows' file manager back when it was simple, fast and good.

Normally, though, I like independent enforcement of data integrity, and PostgreSQL is free, easy to set up and maintain.

Re: Ask HN: What's your go-to back end for simple projects?

#44

Rails. You get lots of great stuff out of the box. Perfect for me to get up and running quickly for simple/side projects. Writing Ruby feels nice and is always a welcome change of pace from a lot of the heavy JS stuff I am doing on frontend atm.

I second Rails. Besides that it provides lot's of out of the box features, there are tons of useful gems. There is also really interesting new API-only mode.

Re: Ask HN: What's your go-to back end for simple projects?

#45

Rails. You get lots of great stuff out of the box. Perfect for me to get up and running quickly for simple/side projects. Writing Ruby feels nice and is always a welcome change of pace from a lot of the heavy JS stuff I am doing on frontend atm.

+1 for Rails.

When i have a new idea it takes me at max a hour to have to complete framework up and standing (Bootstrap/UI, User management, Databases, Deployment, ...) and i can start working on business logic.

Re: Ask HN: What's your go-to back end for simple projects?

#47

C. Why the hell does everything have to be a web app?

C is usually the wrong choice for non-web apps too.

Why?

With GCC's ability to deploy to just about every architecture, most heavy-handed libraries using C themselves (hence a C FFI in higher languages), and access to the biggest and best GUI libs.

Add in musl and static compilation, you get:

* Probably fast

* Native UIs

* Tiny binaries that are easy to distribute

Re: Ask HN: What's your go-to back end for simple projects?

#48

C. Why the hell does everything have to be a web app?

Why the hell can't C be in the web?[1] 1. https://medium.com/@lucperkins/web-development-in-c-crazy-or...

I've used libmicrohttpd for a client in the past.

It was easy, and ridiculously fast.

Re: Ask HN: What's your go-to back end for simple projects?

#50
post #18

Flask! It's Pythonic and good. Once you've done a couple of Flask projects, you can spin up a new microservice in a couple of hours. It's much lighter weight than Django, so it forces you to keep fewer moving parts in your head while hacking. http://flask.pocoo.org/ Lately, I've been using Flask on the back-end, and React on the front-end.

It's more lightweight than Django until you add packages for all of the components you need to build a production-grade app. To get what Django has out of the box requires a half-dozen packages, and even with that Flask-Admin is super primitive compared to what Django Admin provides. I try to like Flask, and I currently run my small personal site in it, but almost every project I start in Flask, I end up rewriting in Django.

As far as building APIs goes, Django Rest Framework provides so much. I find myself reinventing a lot when I use Flask vs Django + DRF. Just my 2¢.

Post reply on HN