API composition. The clandestine pattern in microservice architectures?


When thinking about microservice architectures what typically comes to mind? I would say bounded context, database per-service, containers, service choreography, event sourcing, CQRS, sagas, to name a few. Orchestration isn’t one of them!

The idea of a service directly calling other services to implementing some logic is often inconceivable and considered an anti-pattern. On the flip side, doing such thing is not uncommon either as the means to avoid client-side code having to make multiple API calls or simply as the means to fulfil gaps in functionality. So, what’s going on?

Although in an ideal world API composition as a pattern may not be required, in the real world, it may represent a real and viable option to solve a problem, especially when combined with service-mesh technologies that make service-to-service communication more reliable and fault-tolerant.

Through architectural illustrations and code demonstrations, this talk explores a viable approach to implement API composition in the context of microservice architectures.

Microservices Architectures
Microservice API

Luis Weir


Father, Author, Blogger and Speaker, Luis Weir is a Director of Technology at Oracle and a former Chief Architect at Capgemini. An API/Microservices evangelist, Luis is very passionate about modern technologies and has over 17 years of experience implementing complex systems in many parts of the world. Co-author of 3 API titles and author of the recently published book Enterprise API Management (July 2019), as well as many articles and white papers, Luis is a frequent speaker at events such as Devoxx, CodeOne, Java2Days, NordicAPIs and many other user groups. Luis holds an MS in Systems Integrations from Universitat Politecnica de Valencia and a BS in Electronics Engineering from UNE.