3 ms·
Backend: Django (Python 3.5+). Yes flask might be lighter etc, but at the end of the day, when you need to do things quick, batteries included approach goes a l
by harel 9y ago
Backend: Django (Python 3.5+). Yes flask might be lighter etc, but at the end of the day, when you need to do things quick, batteries included approach goes a long way. Also, it will be easier to find developers who can hit the ground running. Most of the time, I would use it for an API layer coupled with Django Rest Framework.
Database: PostgreSQL 9.6. That's easy. You get the best of all worlds here. RDBMS with indexable JSON document store. Stable, fast. There is no other choice for me.
Front end: Depends. React/Redux works for me 80% of the time. I prefer to use Semantic-UI (the React port is excellent) for the presentation. The other 20% are simple admin only apps where plain old html would do just fine. I now try to avoid all-in frameworks which tie you in like a Catholic marriage.
Async: Celery + RabbitMQ. It works, and works very very well as a background task/job runner.
Source control and Project Management: Git and Github.
Specialised system apps - Go(lang). For fast specialised servers, websockets, etc.
Deployment/Provisioning: Ansible.
Bonus points: Personal Development: Learn a new language every year. Do a little project in it.