O'Reilly logo
  • Derek Harmon thinks this is interesting:

This can be XML, JSON


Cover of Microservices for the Enterprise: Designing, Developing, and Deploying


This is merely a technological platform choice, and sacrifices the whole freedom of each microservice to be built upon whichever technology stack it prefers best.

The "vocabulary" of the XML, JSON, or messages however is subject to the ubiquitous language choice.

Certainly, an Architect should select a published language to use in his/her microservice architecture as a standard, at least across boundary contexts where questions or conflicts would otherwise arise. What this section considers a "pattern" seems sometimes frivolous.