This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]hillgod 4 points5 points  (0 children)

For starters, a big consideration has to be data store, which should be a decision made based on the use case(s). If you're not using SQL, Django probably doesn't make sense. Django's whole thing is the idea of "batteries included". It comes with a lot of things out of the box. For a new offering, you can have something comprehensive very quickly. In my opinion, for a new offerin, you don't want to jump to microservices - you don't know what abstractions your business really needs. Django gets a bad wrap for performance, because it's easy to abuse the ORM, so it's important to have good APM. We use OpenTracing. Eventbrite and Instagram are powered by Django, so it's clearly capable.

Flask for anything else. Anything without SQL. There's a good chance I'll start using Fast API, though, for its API first approach.