Microservice design patterns for line of business applications

So you broke up your big, unmaintainable monolithic system into microservices. Good for you. Each piece is now easy to understand and maintain. Except things didn't get simpler. You've got lots of dependencies between your services to implement your business processes. You're having to modify many services to change your processes and the complexity is exploding. This isn't any better, if you can't improve things you're going back to the old way of doing things. This talk discusses how you can use just three simple architectural patterns to design and implement microservice systems that can isolate the complexity of changes and support managing the evolution of business logic and processes over time. As a bonus it includes other buzzwords like event sourcing and CQRS at no extra charge. Process managers also deal with the distributed non-transactional nature of the system.