Ask HN: Why Not Microservices?
📰 Hacker News · rajacombinator
Learn why microservices may not be the best choice for every company and how to evaluate their suitability
Action Steps
- Evaluate your company's scaling needs using the 2-pizza team rule
- Assess the complexity of your system and whether microservices would simplify or add to it
- Compare the benefits of microservices, such as fault tolerance and scalability, to the added complexity and overhead
- Consider alternative architectures, such as monolithic or modular monolithic, for smaller startups or less complex systems
- Research case studies of companies similar to yours that have successfully implemented or rejected microservices
Who Needs to Know This
Software engineers, architects, and product managers can benefit from understanding the pros and cons of microservices to make informed decisions for their organizations
Key Insight
💡 Microservices can add complexity and overhead, and may not be suitable for small startups or less complex systems
Share This
💡 Microservices aren't for everyone. Evaluate your scaling needs, system complexity, and alternatives before deciding
Key Takeaways
Learn why microservices may not be the best choice for every company and how to evaluate their suitability
Full Article
It’s pretty clear that microservices have fallen out of favor on HN. As someone who’s currently experiencing pain on both sides pro and con here, I’m curious to learn more about the argument. Is there more to it than “you’re not Google, don’t act like Google” for small startups? How about companies that are scale?
DeepCamp AI