The services in a microservice architecture must be loosely coupled and so cannot share database tables. What’s more, two phase commit (a.k.a. a distributed transaction) is not a viable option for modern applications. Consequently, a microservices application must use the Saga pattern, which maintains data consistency using a series of local transactions.

In this presentation, you will learn how sagas work and how they differ from traditional transactions. We describe how to use sagas to develop business logic in a microservices application. You will learn effective techniques for orchestrating sagas and how to use messaging for reliability. We will describe the design of a saga framework for Java and show a sample application.

Microservices almost seem to be the de facto way to build systems today, but are they always the answer? If they are the answer, what are the challenges you'll face at scale (both from a technical and organizational level)? What are the strategies you should use now that you are effectively building a distributed system? ...or what's the one thing you wish you'd known before you got here? These questions and more will be asked in the Microservices: Pattern's & Practices Ask Me Anything or AMA (a significant portion of the time will be available for the audience to get their questions answered as well). This session joins together many of the conference's most popular sessions speakers with the trackhost from the Microservices track to have a frank and honest discussion on Microservices. Join us to have your Microservices questions answered.