Scalability choice

Question

Ok, so a group of friends and I are developing a startup, which we hope will eventually receive about 3 million requests a month within the span of 5 years. Our options are Django or Laravel. Which do you think is more scalable? We don't plan to switch backends or scale up infrastructure for at least 5 years, and we also have a short-paced time span of 1 year or less. I'm totally into Laravel and I have substantial skills with Python too. My concern is investing time into Learning Django to make the switch. Should I? (If Django is a better choice)

refer61614 · Accepted Answer

The shortest path to shipping the first version to users is the right answer. You don't need to worry about 3M requests a month before 20 people give a crap about your product. Pick what's easy for your team.

FrankieDa · Answer

Levels is the epitome of scaling simply and quickly, would definitely check out their blog post on how they used Google Sheets to move a lot faster while still being able to scale it up

https://www.levels.fyi/blog/scaling-to-millions-with-google-sheets.html

mostrovoi · Answer

I think It is more important to get concepts right like DDD and modularized monolith rather than focusing on one framework or another. Define your bounded contexts, use hexagonal and then future promotions to ms or even swap frameworks becomes way way easier

Brandin Chiu · Answer

The other answers here of deprioritizing framework choice and just _launching_ are probably the most correct.As an aside, I'll actually offer an alternative, which would be Symfony over Laravel. It's quite a bit lighter, and is less opinionated without being an empty shell. Laravel is basically built on Symfony anyway.(this is assuming that you're not going to run into architectural issues with what you're building where language choice might matter)

clicketyclack · Answer

3 million requests a month? Who cares what framework you use! Flip a coin if you have to. This doesn’t matter at all. If you’re focusing on this you are focusing on completely the wrong thing. SHIP!

Scalability choice

About

Tech

Members