Timeline for How to avoid synchronous communication between microservices
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 30, 2018 at 14:30 | history | edited | Florian | CC BY-SA 3.0 | added 107 characters in body |
| Mar 30, 2018 at 14:28 | comment | added | Florian | Well there is a difference between asynchrous communication and async i/o. | |
| Mar 30, 2018 at 14:18 | answer | added | Devang | timeline score: 4 | |
| Mar 30, 2018 at 14:18 | comment | added | Erik Eidt | I think you might be looking for the terms request-reply or request-response vs. one way messaging. Messages are only synchronous or async with respect to the internal threading architecture of the sender/receiver, as to whether they are blocking of main/other work vs main/other work can continue while awaiting (e.g. servicing other clients). On the wire, outside of an implementation, a message is neither sync nor async. | |
| Mar 30, 2018 at 13:40 | review | Close votes | |||
| Apr 12, 2018 at 3:02 | |||||
| Mar 30, 2018 at 13:29 | history | edited | MetaFight | CC BY-SA 3.0 | added 2 characters in body |
| Mar 30, 2018 at 13:18 | history | asked | Florian | CC BY-SA 3.0 |