This can be XML, JSON
- 2. Designing Microservices
- from Microservices for the Enterprise: Designing, Developing, and Deploying
- Publisher: Apress
- Released: November 2018
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.
Share this highlighthttp://www.safaribooksonline.com/a/microservices-for-the/20435852/