interpreted under the corresponding context
- 2. Designing Microservices
- from Microservices for the Enterprise: Designing, Developing, and Deploying
- Publisher: Apress
- Released: November 2018
I can see using namespaces here to scope the Customer entity across microservices, but having four different variations of a Customer sounds like a problem to me.
Each microservice could well be implemented on its own technology stack: .NET, Java, and Python. Namespace scoping may not be relevant, and this may make each Customer simpler in its own microservice because it is not burdened with the fields of Customer entities in the other microservices. Agreement on a common identifying key may still be necessary, however.
Share this highlighthttp://www.safaribooksonline.com/a/microservices-for-the/20434144/