I'm working on a Chat app and I'm currently using 2-4 real time connections each with its own instance. I can control the data using riverpod but there's certain things that I want to change when the database does. I'm just trying to find out if I'm gonna regret using too many real time connections per user
self-hosted or cloud?
Self-hosted
I got a decent server setup
It depends on what your server can handle then
Okay
Good answer
Are you familiar with riverpod?
Is the only way I can get updated info from a stream provider
I think I'm doing something wrong because when I use a state notifier when I post a chat it doesn't show till I refresh
Or hot reload
There are some os level tweaks you may need to handle the open connections: https://itnext.io/websocket-1-million-connections-using-appwrite-2d2a2c363a37
Ohhh what's that
Probably considering the data comes from a stream
Wow
What an awesome article
I need to learn how to make better riverpod providers
Wow for 1k a month I can have 1 million real time connections
Appwrite is awesome
I bet I'd have to pay like 10k if I was using firebase
If you know any good resources for how I can be better with appwrite requests and real time let me know. I love learning
just keep building stuff and try to think of ways to optimize. best way to learn imo, is to build, break and rebuild
Sounds good π @safwan
[Solved] how many real time connections are too much
Recommended threads
- RealtimeResponseEvent Typescript Bug
Hello, could you please fix RealtimeResposneEvent, the one in realtime.ts have timestamp: string, but the one in client.ts have timestamp: number, and it causes...
- Realtime Docs are outdated
The Realtime docs are outdated.
- Fine grained permissions for webRTC hand...
Hi, I am building a WebRTC P2P app for a university project and have hit a security limitation regarding permissions for anonymous users. The Architecture: We ...