Hello guys!
I have a question regarding what kind of backend is better to use.
Let's assume:
Im developing an application that provides realtime information, and will be used from million of users.
I like the structure of a Django project(i dont call app because in Django app u have inside apps) where u can generate apps and somehow decouple things. Also it very easy to use and the framework is batteries included. This backend would serve a mobile app.
On the other side there is JS backend frameworks like express and so on but there you can do things in every way u like. You dont have some agreements of development way as in Django for example. But JS is fast(how I read in www).
What I want to say is that for such an application what will be better to use if we assume that:
we need to handle a lot of requests.
we need to have an ease when we develop.
we need to have some agreement/rules in what way need the app(for example APIS) to be developed.
Im not a super experienced developer, im trying to figure all this things out. I really like the skill of programming because it gives u something that I call FREEDOM. FREEDOM to create things that solve problems.
Anyways I would like to thank you in advance for your answers!
Top comments (5)
In my experience you can get something done faster using django, and if you use some easy to use PaaS, you can avoid much effort in DevOps and similar things.
If PaaS is not an option, DevOps will be an extra effort, and in the future you will have to think of other abstractions at the cointainer level unless you go the serverless route. Which, although possible with django, it's not the best setup, in my opinion, unfortunately.
PS: If you end up going the serverless route, i recommend typescript by the way. And the benefit of serverless would be saving the devops and maintenance effort.
Thank you Bulletninja! Need to balance faster & stable :) I will think how to do it!
What makes you certain to get "million of users"?
We hope for the better :D
Just want to say: don't try to pay too much attention on future scaling issues, yet. Pick the tools that you're comfortable to work with, which do the job right now. The good thing is: when you face scaling issues, you'll probably have so many users that you can afford a team working on scaling. Maybe they will need to rewrite some parts of your tools, maybe not - it's not the right time to think about that for now.