Timeline for What is a canonical schema in a context of microservices architecture?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 16, 2016 at 13:45 | vote | accept | Arseni Mourzenko | ||
| Nov 16, 2016 at 10:54 | comment | added | Paul | Yes, though the sharing isn't necessarily at the DLL level as you still might have a heterogeneous architecture from the app implementation perspective. One endpoint might be in Java while another in .NET, for example. So the shared model would be defined in a neutral language (e.g. XSD) and then each endpoint uses that as a mechanism for schema enforcement. | |
| Nov 16, 2016 at 4:19 | comment | added | Arseni Mourzenko | So the SOA's canonical schema consists of sharing a data model between the service and its consumer, such as, in .NET, the same data model assembly being used by both the service and the consumer projects. Microservices approach, on the other hand, consists of not sharing a data model, but, for the consumer, to rely on whatever part of the message it needs (for instance by walking manually through the JSON message). Is my understanding correct now? | |
| Nov 16, 2016 at 3:49 | history | answered | Paul | CC BY-SA 3.0 |