正在加载视频...

视频加载失败

im building the best next.js stack to ever exist i just found out cloudflare workers natively support long-running websocket connections - extremely cheap - reliable af & fully serverless - zero infra to manage you can setup real-time next.js in literally seconds

52,539 次观看 • 1 年前 •via X (Twitter)

10 条评论

Josh tried coding 的头像
Josh tried coding1 年前

this is the API i'm thinking of for jstack (the next.js/typescript stack im building), probably doesnt get simpler than this if i now find a way to make the messages type-safe its over

Irteza Bangash 的头像
Irteza Bangash1 年前

Yp I've been playing with cf workers and its crazy good. Looking forward to trying the jstack

chronark — oss/acc 的头像
chronark — oss/acc1 年前

Is this integrated into @upstash with a db, vector and workflows?

Josh tried coding 的头像
Josh tried coding1 年前

@upstash vector and workflows no, a redis db yes because that powers the bidirectional comms. you could also use cloudflare durable objects, but i prefer upstash

Alchemist 的头像
Alchemist1 年前

You can use durable object for this

Carlos Ziegler 的头像
Carlos Ziegler1 年前

How about self hosted ?

Josh tried coding 的头像
Josh tried coding1 年前

should be possible by just switching out the url to your own ws server, but not nearly as convenient

Umair 的头像
Umair1 年前

Pr?

Firat Özcan 的头像
Firat Özcan1 年前

If you go the path of using durable objects for your rooms (which you should), you do need to solve the issue of those objects being fixed to the location of the first request. May not be what you want, some solution for migrating it closer to the user may need to be built by you

Josh tried coding 的头像
Josh tried coding1 年前

not a problem when using upstash redis realtime subscriptions as we do in the demo, i find durable objects to be pretty unintuitive

相关视频