Most gateway tutorials stop at "here's how you route a request." That's the easy 20%. The hard part is what happens when a client hammers you with requests, a downstream service falls over mid-traffic, or you're staring at a 500 trying to figure out which of your four services actually caused it.
Most gateway tutorials stop at "here's how you route a request." That's the easy 20%.
The hard part is what happens when a client hammers you with requests, a downstream service falls over mid-traffic, or you're staring at a 500 trying to figure out which of your four services actually...
I tried to make it behave like one вЂ" including the annoying bits, like config tradeoffs and races that most demos just quietly ignore.
The page is ready to read now. The fuller skim-friendly version will appear here automatically.
Most gateway tutorials stop at "here's how you route a request." That's the easy 20%. The hard part is what happens when a client hammers you with requests, a downstream service falls over mid-traffic, or you're staring at a 500 trying to figure out which of your four services actually caused it. I tried to make it behave like one вЂ" including the annoying bits, like config tradeoffs and races that most demos just quietly ignore.
I wanted to build something that hits those problems on purpose, so I put together spring-gateway-sample: a public gateway, an api-server that fans out to two downstream services, and a full observability stack sitting behind all of it.
Open the app view to save this story, compare related coverage, and continue from the same source.