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.
Hi HN,I’m building Feato, a developer-first feature flag service focused on real-time delivery without polling.The core idea is simple: applications establish a persistent connection and receive configuration changes as events, instead of repeatedly fetching flags on an interval.Why I built this: In many projects I’ve seen feature flags implemented via polling, which adds latency and...