Microservice Architecture at Medium (medium.engineering)
At Medium, our technical stack started with a monolithic Node.js app back in 2012. We have built a couple of satellite services, but we haven’t created a strategy to adopt the microservice architecture systematically. As the system becomes more complex and the team grows, we moved to a microservice architecture in early 2018. In this post, we want to share our experiences of doing it effectively and avoiding microservice syndromes.
It’s been years since we started talk about switching to microservices architecture from monolithic app. It’s worth reading how large scale companies have successfully went through the switch and what are their principles and strategies to get full benefits of microservices.
More stories about embracing microservices:
- LinkedIn: Q&A with Jim Brikman: Splitting Up a Codebase into Microservices and Artifacts
- Uber Service-Oriented Architecture: Scaling the Uber Engineering Codebase As We Grow
- Shopify: Deconstructing the Monolith: Designing Software that Maximizes Developer Productivity
- Squarespace: The Pillars of Squarespace Services
- Netflix: Adopting Microservices at Netflix: Lessons for Architectural Design
- Box: Kubernetes at Box: Microservices at Maximum Velocity