I really get confused with this terms Orchastrator vs choreography .
They both look like SOA vs Microservices architectures.
In SOA(Orchastrator) would have ESB(mulesoft/tibco/neuron) which would abstract the target services so you will get loosely coupled endpoints & addition of end points are also easier.
In Microservices (Choreography) you have queue/topic which will be subscribed interested parties which is very much loosely coupled i get this idea.
But it confuses me with SOA paradigm where u r also getting same benifits. So what's the point?, if scaling is problem you have your taget services already independent can be scaled.
Or Am i mixing stuff , can anyone enlighten me.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I really get confused with this terms Orchastrator vs choreography .
They both look like SOA vs Microservices architectures.
In SOA(Orchastrator) would have ESB(mulesoft/tibco/neuron) which would abstract the target services so you will get loosely coupled endpoints & addition of end points are also easier.
In Microservices (Choreography) you have queue/topic which will be subscribed interested parties which is very much loosely coupled i get this idea.
But it confuses me with SOA paradigm where u r also getting same benifits. So what's the point?, if scaling is problem you have your taget services already independent can be scaled.
Or Am i mixing stuff , can anyone enlighten me.