So you've finally broken up your monolithic app into a more manageable set of micro-services that are decoupled from each other and have clear responsibilities. Hooray you've reached the Martin Fowler promised land of micro-services bliss!

Then a pesky user shatters your hopes and dreams with real business requirements. To fulfill the requirement you will need...

1. Data that is contained within multiple services
2. Actions will need to be performed on multiple services
3. A long running business process that has both automated and manual steps

In this class we (including you!) will help a scrappy startup named Meatify that is revolutionizing the meat wholesale business. They built v1.0 of MMS (Meat Management System) using a microservice architecture and are experiencing growing pains from the coupling they have introduced between their services and the information silos that is preventing their users from a getting a holistic view of the system. We will evaluate how the Orchestration and the Choreography patterns can be implemented to address their problems.

Intended Audience:
Software designers, developers, and professionals. We will keep things pretty high level so it will apply to a wider field than you might expect including Data Modeling, Business Architecture, Software Architecture, and Software Engineering.