What I found was that people on my team were jumping to conclusions based on shallow but dangerously firm notions of what a microservice was. They held knowledge that microservices were small API’s pieced together to create whole systems. But they weren’t aware of the intricate tradeoffs and design considerations that can mean the difference between success and failure.
How Teams Get Microservices Wrong From the Start
Abi Noda
2.2K11

Monoliths are not dead or evil; its just not as appropriate in some situations. Same can be said for microservices.

IMO, take away ESB from traditional SOAs, you got more or less microservices. However, the integration role is now played by loadbalancers, messaging, clusterings, what not. You just substituted one form of complexity with another one. Its not all peachy keen in the microservices world.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.