5 ms·
This is a related issue and possible counter example - how do you define datastructures passed around microservices? Serialized objects ala protobufs? Versioned
by rb808 10y ago
This is a related issue and possible counter example - how do you define datastructures passed around microservices? Serialized objects ala protobufs? Versioned XML or JSON? Schema versioned docs?
This is a great opportunity to have shared libraries or at least schemas across different microservices. In fact having each service write their own parsers or serializers would be a mistake for me.
- c0wb0yc0d3r 10y agoI think you would use protobuff, XML, JSON, etc. The idea would be that you encapsulate all of your services behind a gateway of sorts. External clients would interact with the gateway only, and internal services would just provide a one size fits all response. This way front end teams are responsible for their clients and there is very little change internally because every base is covered in the general purpose response.
- z3t4 10y agoi think a lot of people mix up micro services with distributed systems. two different services for example the smtp service and the http service should not need to communicate internaly. they should be able to deploy independent of each other. a mailform service will need to communicate with both, but a common language between all services is not needed. JSON is popular though.