Reading in this space is interesting because it also points out contradictory explanations in evolving areas. Just listened to
on Youtube. Neal Ford If you’ve looked at the NGINX Microservices — From Design to Deployment, you find things like
-
The API Gateway is responsible for request routing, composition, and protocol translation. - The API Gateway will often handle a request by invoking multiple
microservices and aggregating the results.
There are some other things here that raises Martin’s question o whether the API Gateway starts looking like an ESB.
Neal Ford, working for ThoughtWorks at the time of the video, pillories the ESB and emphasizes dumb pipes and smart endpoints. While the NGINX story has the API Gateway doing things like composition, Ford talks about the first (micro)service called will take on the role of the orchestration controller or each service knows the next service in the pipeline and choreography is used for control.
This looks like a question for NGINX.
The NGINX stuff is still the only one I’ve seen that gets into detail of what one does to get eventual consistency — through event processing in their work — and synchronize each microservice’s local data store.
Should probably look more into ThoughtWorks material.
Ken
------------------------------------------------------------------------------
Dr. Kenneth Laskey
MITRE Corporation, M/S F510 phone: 703-983-7934
7515 Colshire Drive fax: 703-983-1379
McLean VA 22102-7508