4 replies
by rproffitt edited
"You're Not Building Netflix: Stop Coding Like You Are" is a good read at https://dev.to/adamthedeveloper/youre-not-building-netflix-stop-coding-like-you-are-1707
Let's skip over the NOT A PROBLEM speed hits over high quality graphics. YOU ALREADY KNOW THIS. No need to go over such ground.
About scale. You buy scale with more compute or server power at AWS or such so that's not a worry either.
The BIGGEST PROBLEM I see is the team get DERAILED over performance and scale.
Get it working first. Get it deployed FIRST. Don't think for a second it has to scale to Netflix scale.
by birdmantd
by BenDunk8190
by AailaKhan09
Great question. From my experience, the biggest long-term impact usually comes from decisions made very early around architecture, data handling, and performance budgets. Things like choosing a scalable hosting setup, keeping the codebase modular, planning for caching and CDN usage early, and avoiding over-engineering at the start make a huge difference later.
I’ve also seen that clear conventions (naming, folder structure, API contracts) and good documentation pay off more than expected as teams and traffic grow. You can always optimize features later, but fixing poor foundations at scale is much harder.
This discussion is closed to new replies.
Trending Web Development posts
Sort by Trending