Hacker News is a community-driven platform for sharing and discussing technology news, startups, and programming-related topics. Through user submissions and comments, Hacker News offers insights into emerging technology trends, industry developments, and entrepreneurial ventures. Readers can participate in discussions, share their insights, and stay informed about the latest advancements in technology and innovation.

Hacker News

Twilio Segment migrated from 140+ microservices back to a monolithic architecture after microservices created unsustainable operational overhead. The team consolidated separate repos and queues into a single service with a unified test suite using Traffic Recorder. This transition dramatically improved developer productivity (46% more library improvements), reduced deployment complexity from 140+ services to one, and simplified scaling. While accepting trade-offs like reduced fault isolation and less effective in-memory caching, the monolith proved more suitable for their server-side destinations pipeline.

Goodbye Microservices

Learn. Share. Grow. By devs for devs - a place for sharing information useful to any developer no matter what path they are on. 

Devs Together Strong

Since this is a 2018 post, does anyone know if they still using a monolith?

If you build a software microservice without a solid reason, then it’s possible to back a monolithic architecture because you are confused about which one is best for you. Before convert microservice or a monolith, you should know which one is right for you and why.

I think people should default to modular monoliths, then whenever needed start transforming to what’s called “planet and satellite” approach, where you transform a single small module to a microservice (bcz of high traffic to that particular module…etc) while keeping the rest as is ( as monolith).
The main drawback of this approach is if you need database separation when externalizing a module, it can cause some headache.

Both design patterns have complexity and tradeoffs, the complexity is just hidden in different places.

no doubt, monolithic architecture is easily manageable but it is not so much scalable after a scale, then microservice is the way to resolve scalability issue, but it requires more engineering and more people to manage.