ChoreographyOrchestration

%Focusing on \paradigm{loosely coupling} means to pay attention to the communication between services. Researchers distinguish between \paradigm{Orchestration} and \paradigm{Choreography} based architecture %%\parencites[p. 43]{newman2015building}{peltz2003choreography}. %\cite{newman2015building,peltz2003choreography}. %%While the first requires the implementation of a central service that handles all communication between other services, architectures using the second principle implement communication based on events or publish / subscriber mechanisms \cite{peltz2003choreography}. %While the first is used to control a process breaking the service boundaries, the second approach distributes responsibility for collaboration between the services. Therefore \paradigm{Orchestration} requires a central service that handles all communication between other services. In contrast, architectures based on %\paradigm{Choreography} implement direct communication%% \cite{peltz2003choreography}. %, like event systems or publish / subscriber mechanisms \cite{peltz2003choreography}.

%Middleware (3-tier) applications, service bus architectures and transaction monitors are possible implementations for \paradigm{Orchestration} \cite{namiot2014micro,viennot2015synapse}. In contrast, \paradigm{Choreography} often depends on event systems or publish / subscriber mechanisms \cite{peltz2003choreography}.

Todo: Ausformulieren!