[Solved] how many real time connections are too much

[vague wedge]

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

[night haven]

self-hosted or cloud?

[vague wedge]

Self-hosted

I got a decent server setup

[night haven]

It depends on what your server can handle then

[vague wedge]

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

[night haven]

There are some os level tweaks you may need to handle the open connections: https://itnext.io/websocket-1-million-connections-using-appwrite-2d2a2c363a37

[vague wedge]

Ohhh what's that

[night haven]

Probably considering the data comes from a stream

[vague wedge]

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

[edgy cedar]

just keep building stuff and try to think of ways to optimize. best way to learn imo, is to build, break and rebuild

[vague wedge]

Sounds good 👍 @edgy cedar