News for hackers. Stuff that matters.

A comment on Microservice Trade-Offs. Parent comment

Re:Microservice Trade-Offs by wpietri on Wednesday July 01, 2015 @12:42PM (#9813189)
Yes. A friend is at a company that went from a monolith to a microservices approach. (The service-to-engineer ratio is something like 1:2.) He says it's radically better because somebody after a new feature can mainly just compose existing services. But they had hundreds of employees before they made the switch.

Personally, I would start sooner than that. I think new technologies make service creation easier. But the right moment for me depends a lot on product, team, and tech.

[ Parent | on HN ]
Re:Microservice Trade-Offs by apalmer on Wednesday July 01, 2015 @02:40PM (#9814179)
Most of the 'problems' with microservices are in the operations phase, not typically in the development phase.
[ Parent | on HN ]
Re:Microservice Trade-Offs by wpietri on Wednesday July 01, 2015 @07:48PM (#9816041)
Do serious shops have phases for these things anymore? In my view a modern shop should be developing and releasing frequently, and that engineers should experience operational consequences of development choices.

So I guess I would say that any place not working like that might not be ready for a microservices approach.

[ Parent | on HN ]