Timeline for API Gateway (REST) + Event-Driven Microservices
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 29, 2020 at 17:12 | comment | added | rmustakos | What it seems you are describing is a polling architecture. The client can start an async processing request on the server. The server goes off and processes the request and finishes processing at some point. In the meantime, the client gets to the point where it wants the processing results. The client tries to get it from the server, but it isn't done, so it comes back again later. That is polling. | |
| Apr 18, 2018 at 17:12 | history | edited | Jack | CC BY-SA 3.0 | added 1 character in body |
| Oct 19, 2017 at 21:24 | history | edited | Jack | CC BY-SA 3.0 | added 19 characters in body |
| Oct 19, 2017 at 20:07 | history | edited | Jack | CC BY-SA 3.0 | edited body |
| Oct 19, 2017 at 19:35 | history | edited | Jack | CC BY-SA 3.0 | added 17 characters in body |
| Oct 19, 2017 at 12:53 | history | edited | Jack | CC BY-SA 3.0 | added 3 characters in body |
| Oct 19, 2017 at 12:46 | history | answered | Jack | CC BY-SA 3.0 |