Skip to content

[aws]: refactor callout in streaming page #158

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

[aws]: refactor callout in streaming page #158

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions pages/aws/v2/inner_workings/streaming.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
import { Callout } from "nextra/components";

<Callout type="warning" emoji="⚠️">
Streaming support is **EXTREMELY EXPERIMENTAL**... AWS has updated their runtime in the past which broke streaming... It seems stable now but if they do another rugpull, it could cause your app to break.

**It's not recommended to use streaming in production.**

<Callout variant="info">
Streaming in AWS has been stable for a while now. There has been some trouble with AWS breaking the
streaming functionality in the past. It seems to be working well now. If you have an issue with streaming
send a message on [discord](https://discord.com/channels/1283128968140161065/1286094576788177059) and
contact AWS support to let them know of the issue.
</Callout>

Streaming is using the new AWS lambda support for [streaming responses](https://docs.aws.amazon.com/lambda/latest/dg/configuration-response-streaming.html). This allows you to send data to the client as it's generated instead of waiting for the entire response to be generated.
Expand Down