What is the main operational risk when proxying streamed responses?
Timeouts and backend deadlines can silently defeat a long-lived stream. Google documents a default HTTP stream timeout of 15 seconds and a maximum of one hour, so clients, gateway settings and backend behavior must agree on the intended connection lifetime.
Answered in
Google Cloud API Gateway Adds Streaming. The Timeout Becomes Part of Your APIGoogle Cloud's streaming preview routes SSE, WebSockets and gRPC through API Gateway, but backend deadlines and creation-time choices need planning.
Read the full analysisOther questions this article answers
More development best practices questions
- Does GitHub’s new storage architecture change Git commands?
- Why separate Git objects from references?
- Is the new architecture generally available?
- Does the new overview page change pull request merge requirements?
- What does GitHub’s pull request overview show?
- Is the overview page enabled by default?
- What streaming protocols does Google Cloud API Gateway support in preview?
- Can an existing API Gateway API be changed to streaming later?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the Development Best Practices beat.