With popular poster children such as Netflix and Amazon, using microservices-based architectures seems to be the killer approach to twenty-first-century architecture. But are they only for Hollywood coders pioneering the bleeding edge of our profession? Or are they ready to be used for your projects and customers? This session goes over the benefits, but more so the pitfalls, of using a microservices-based architecture. What impact does it have on your organization, your applications, and dealing with scale and failures, and how do you prevent your landscape from becoming an unmaintainable nightmare. This presentation goes beyond the hype and explains why organizations are doing this and what struggles they need to deal with Blog: https://blogs.oracle.com/java/microservices-for-mortals Where did it come from? (6:00) Microservices are about Business Agility (10:06) Monoliths (20:00) Initial Investment (23:55) Data Strategy (27:14) Synchronous vs. Asynchronous (32:10) Re-use Traps (35:14) Dealing with Failure (43:49)

Comments

1. how do you avoid reuse and at the same time do not have more than one microservice accessing and updating a database model?