Timeline for Avoiding Synchronous Communication Between Microservices
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 4, 2023 at 21:00 | comment | added | The Corn Inspector | @Laiv Thanks, and so sorry to reply to this a year late! I'm just curious about the security implication of doing that - isn't it unsafe to pass intermediary data to the client when it could be avoided (especially in the case of sensitive info like credit cards)? | |
| Oct 19, 2022 at 10:29 | answer | added | pjc50 | timeline score: 3 | |
| Oct 19, 2022 at 10:17 | answer | added | LikeLikeAteMyShield | timeline score: 1 | |
| Oct 18, 2022 at 17:07 | review | Close votes | |||
| Oct 23, 2022 at 3:06 | |||||
| Oct 18, 2022 at 15:30 | comment | added | Laiv | The Client asks the CustomerService first and only when it has the CreditCard and makes a call to the OrderService. Basically, the client orchestrates the steps to reach the last one. To decouple services, you must embrace the idea that services are "agnostic" to the source of the data they get as input. They expect the input, they don't go for it. They are only responsible and accountable for the outputs. | |
| Oct 18, 2022 at 5:58 | answer | added | mtj | timeline score: 2 | |
| Oct 17, 2022 at 20:54 | answer | added | Robert Bräutigam | timeline score: 10 | |
| S Oct 17, 2022 at 20:17 | review | First questions | |||
| Oct 18, 2022 at 3:40 | |||||
| S Oct 17, 2022 at 20:17 | history | asked | The Corn Inspector | CC BY-SA 4.0 |