Загрузка видео...

Не удалось загрузить видео

На главную

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

Похожие видео