The streaming limitation to overcome is that Bubble’s API connector will not allow streamed responses. Aside from using webhooks (please don’t do it) to get a streamed response, there’s no other way aside from using a plugin.

So, now that’s out of the way:

  1. Existing plugins are varied in their approach but accomplish the same thing, which is that you send off a prompt, and it streams back the response that you can access from a state on the plugin element.
  2. Some plugins expose API keys - choose one that doesn’t
  3. Some plugins route via the plugin owner’s server, which may have data privacy implications and it can in theory be shut down at any time

So, a serverless function alone won’t get you the streamed response, because you still need to get over the Bubble limitation of not being able to have streamed responses from the API Connector (which is why we use a plugin).

Much the same… I just go with Google Cloud Functions as I find it pretty easy to set up and I keep all my clients on the same provider for ease of management.

Does he really though, or does he think he does without knowing what that actually means?

No difference - whether you use Buildship or a custom code, you still need to use a plugin to overcome the streaming limitation. Bubble backend, BuildShip, custom code - none of them alone will allow you to stream text. Bubble backend definitely won’t allow you to. Buildship and custom code probably will.

1 Like