Timeline for Microservices & Canonical model
Current License: CC BY-SA 3.0
23 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Nov 22, 2016 at 4:39 | history | bounty ended | Punter Vicky | ||
| S Nov 22, 2016 at 4:39 | history | notice removed | Punter Vicky | ||
| Nov 15, 2016 at 22:11 | answer | added | pnschofield | timeline score: 1 | |
| Nov 15, 2016 at 18:55 | comment | added | Punter Vicky | @Laiv bounty is yours :-D | |
| Nov 15, 2016 at 17:35 | comment | added | Laiv | Another better answer might happens still :-). Anyways glad to help you. | |
| Nov 15, 2016 at 17:29 | vote | accept | Punter Vicky | ||
| Nov 15, 2016 at 17:20 | comment | added | Laiv | @PunterVicky It could be a good subject for another question :-) | |
| Nov 15, 2016 at 17:19 | answer | added | Laiv | timeline score: 6 | |
| Nov 15, 2016 at 16:28 | comment | added | Punter Vicky | @Laiv: Regarding ESB , I came across another post where they had mentioned that in traditional SOA approach , the pipes (ESB) are intelligent and endpoints are dumb and in MS approach , pipes are dumb and endpoints are intelligent. Since routing is kind of orchestrated by MS themselves & there is no common bus layer to orchestrate , is the author mentioning that MS has ESB like functionality? But then I thought API gateways sort of do the routing , so am confused too :) | |
| Nov 15, 2016 at 16:24 | comment | added | Punter Vicky | Thanks @Laiv. Your explanation makes sense to me. Please add an answer and I will accept :-) It will be useful for others who come across this and need an explanation. | |
| Nov 15, 2016 at 9:23 | history | tweeted | twitter.com/StackSoftEng/status/798456440776261632 | ||
| Nov 15, 2016 at 8:00 | comment | added | Laiv | But then, what seems confused to me is the previous sentence They also very much avoid using ESBs and instead implement ESB-like functionality in the microservices themselves. | |
| Nov 15, 2016 at 7:59 | comment | added | Laiv | Some data model yes, but seems to me, that the article is referring to a "shared" or "common" data models between 2 or more services. The Canonical schema is a pattern meant to save services from in runtime data transformations. A common "language" between services. So looks like the article is emphasising on the total independence of the MS from the "ecosystem" where it lives at. Take for example the mention it does to ESB. ESB usually demands an enterprise data model (messages) which is going to be common for everyone in the bus. MS rejects to be attached to any external system constriction. | |
| Nov 15, 2016 at 3:17 | history | edited | Punter Vicky | edited tags | |
| Nov 15, 2016 at 3:17 | comment | added | Punter Vicky | Thanks @ArseniMourzenko . I believe even in microservice architecture, the request and response have to comply to some data model. Not unable to understand yet as to why it is referred to as being rejected by microservice architecture . | |
| Nov 15, 2016 at 3:13 | comment | added | Arseni Mourzenko | I suppose this Wikipedia article is what you are looking for. However, I don't find the article easy to understand. | |
| S Nov 15, 2016 at 2:42 | history | bounty started | Punter Vicky | ||
| S Nov 15, 2016 at 2:42 | history | notice added | Punter Vicky | Canonical answer required | |
| Nov 8, 2016 at 2:40 | history | edited | Jack | CC BY-SA 3.0 | added 142 characters in body |
| Nov 8, 2016 at 2:34 | comment | added | Punter Vicky | Sure Jack , it is here - nginx.com/blog/introduction-to-microservices/… | |
| Nov 8, 2016 at 2:31 | comment | added | Jack | Would you happen to know the source of that statement? (for purposes of linking) | |
| Nov 8, 2016 at 2:31 | history | edited | Jack | CC BY-SA 3.0 | Properly format quoted text |
| Nov 8, 2016 at 2:18 | history | asked | Punter Vicky | CC BY-SA 3.0 |