> Much like moving to a cryptographic linked-list with decentralized consensus creates ton of drama, splitting services into as many pieces as possible seems li

> Much like moving to a cryptographic linked-list with decentralized consensus creates ton of drama, splitting services into as many pieces as possible seems like asking for trouble. But it's not about splitting it in as many services as possible. There's also nothing saying you can't live in a hybrid state, you don't need to go 100%. There's plenty of orgs that run a monolith and little by little break out components they need to. Or sometimes build something new as a microservice for other reasons (like the framework/language of the monolith is limiting them to solve a use case) and hook that up to their monolith.