FeatBit originally used WebSocket. Later, we added a polling option based on customer requirements.
Out of curiosity, how do you handle this with Next.js deployed on Vercel?
Next.js / Vercel would typically be on the consumer side.
Feato doesn’t rely on any server-side streaming in the client’s app.
The browser opens an SSE connection (via EventSource) directly to the Feato backend,
which runs as a long-lived service. Next.js is only used to serve the application
and bootstrap the client.
Some platforms impose practical limits around long-lived connections,
even though SSE itself is just standard HTTP.
Feato doesn’t depend on any platform-specific behavior here — it uses
the browser’s native EventSource over HTTP directly to our backend.
Because of that, the client framework or hosting environment
(Next.js on Vercel, CRA, Angular, etc.) doesn’t really affect the real-time channel.
FeatBit originally used WebSocket. Later, we added a polling option based on customer requirements. Out of curiosity, how do you handle this with Next.js deployed on Vercel?
Good question, and just to clarify the context.
Next.js / Vercel would typically be on the consumer side. Feato doesn’t rely on any server-side streaming in the client’s app.
The browser opens an SSE connection (via EventSource) directly to the Feato backend, which runs as a long-lived service. Next.js is only used to serve the application and bootstrap the client.
Some platforms impose practical limits around long-lived connections, even though SSE itself is just standard HTTP. Feato doesn’t depend on any platform-specific behavior here — it uses the browser’s native EventSource over HTTP directly to our backend.
Because of that, the client framework or hosting environment (Next.js on Vercel, CRA, Angular, etc.) doesn’t really affect the real-time channel.