Cloud Architecture/Development, 0
Many developers and architects are familiar with the Microservice Architecture main concepts. Breaking the system to many small autonomous and high cohesive services, reducing the coupling in the system, having better isolation utilizing modern hosts such as Docker containers and so forth. However, having many small moving parts may lead to higher integration and management complexity. In traditional Service-Oriented Architecture, there is usually a controller, or a manager that orchestrates the business flow. Having such a service simplifies the system, but might contradict some of the Micro Service Architecture principals. In the other hand having decoupled services that communicate by publishing messages in a reactive manner, provides the promised Micro Service Architecture flexibility, but introduces the cost of higher complexity. The lecture starts with a short introduction to the Micro Service Architecture. Then, the audience will learn about the orchestration and the chorography service communication approaches, the pros and cons of each of the method and even a method that enables combining the two. With this knowledge the participants will be able to choose the best method that fits their need.