Timeline for Single api gateway or one for each microservice
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 29, 2023 at 11:36 | answer | added | DavidT | timeline score: 1 | |
| Jun 25, 2023 at 10:06 | comment | added | Ben Cottrell | I don't see any coupling here - services behind a gateway should not have any awareness nor dependency on that gateway (That is to say, it should be possible to switch the gateway off and for all of your services to continue to work normally for internal traffic. A gateway is just an entry point for external traffic -- if the services themselves are somehow coupled to the gateway then that's a problem to be solved in itself) | |
| Jun 24, 2023 at 15:01 | comment | added | Sebastian Sotto M. | Having an API gateway for each microservice defeats the purpose of having a centralized entry point for managing and securing your APIs. | |
| Jun 24, 2023 at 6:41 | history | asked | dstr | CC BY-SA 4.0 |