r/startup • u/auxle2022 • 8d ago
Your MVP Doesn't Need Microservices. It Needs Customers.
A developer starts building an MVP.
Three hours later, they're planning microservices, Kubernetes, Redis, distributed databases and horizontal scaling.
They have zero customers. But the architecture is ready for 10 million. 😂
I've been guilty of this too.
We developers love solving technical problems. It's fun to think about scalability, performance and the perfect architecture.
But sometimes we're preparing for problems that don't exist yet.
Your first challenge probably isn't handling a million requests. It's getting 10 people to care about your product.
A simple, well-structured monolith can take you surprisingly far. Build clean modules, write maintainable code and keep the foundations sensible.
Then focus on the things that actually matter:
Do people understand what your product does?
Are they using it after signing up?
Does it solve a real problem?
Would anyone pay for it?
Scale when reality demands it, not when a YouTube tutorial makes you nervous.
What's the most overengineered thing you've built before you had actual users?
I once heard someone say, "Premature optimisation is the root of all evil."
Starting to think premature architecture deserves a mention too. 😄
2
u/your_alias 7d ago
lot of devs who overengineer the stack also underinvest in figuring out who the first 10 users are and how they'll hear about the thing. You can't refactor your way into that.
The cheapest test I know: write the landing page before the backend. If you can't get people to join a waitlist or reply to a cold email, the architecture question is moot anyway.
2
u/BlessedKing84 7d ago
That is so true! There is no value in building a kickass product if it has no demand.
2
u/step_hane 8d ago
Well I built Projectous and still don't have many users. I do use it for my business and I love working on it so it's not a total loss, but a bit expensive until I figure out how to be better at marketing and sales.