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.
Ask HN: What's your go-to back end for simple projects?
41–50 of 65 posts
Re: Ask HN: What's your go-to back end for simple projects?
#42Re: Ask HN: What's your go-to back end for simple projects?
#43I 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.
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?
#44Rails. 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.
Re: Ask HN: What's your go-to back end for simple projects?
#45Rails. 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.
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?
#46C. Why the hell does everything have to be a web app?
Re: Ask HN: What's your go-to back end for simple projects?
#47C. Why the hell does everything have to be a web app?
C is usually the wrong choice for non-web apps too.
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?
#48Re: Ask HN: What's your go-to back end for simple projects?
#49Re: Ask HN: What's your go-to back end for simple projects?
#50Flask! 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.
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¢.