Timeline for How to deal with bad third party APIs in a microservices architecture?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 21, 2020 at 8:12 | vote | accept | abstract christmas tree | ||
| Feb 20, 2020 at 15:39 | comment | added | Aaron M. Eshbach | @abstractchristmastree That can depend on your technology stack a little bit, but I would generally define the facade in terms of my own domain model. The adapter then maps between that and the 3rd-party domain. | |
| Feb 20, 2020 at 7:00 | comment | added | abstract christmas tree | Thank you :) But how do you go about sharing the domain model? I'm currently mapping my own domain model against that of the third party service in the ACL. Tools like swagger-codegen can then generate a client, including the models of my mapped domain, in my aggregator service. | |
| Feb 19, 2020 at 20:56 | history | answered | Aaron M. Eshbach | CC BY-SA 4.0 |