I have a question regarding the concurrent connections: can someone describe what is meant by 500 concurrent connections- is it 500 subscriptions to different endpoints or 500 users using the realtime api no matter how many endpoints they are subscribed to?
And how does the additional billing work? Is it that every time there’s more than 1000 additional connections we are charged, or it tracks the highest number of connections during the month and charges based on it?
Hey @Szh, first of all, during beta, we're currently not officially charging for this. Once we do, the count will be for the highest concurrent connections number in that billing cycle. Only if you exceed your plan limit you'll be charged with additional addons. If your budget cap doesn't not allow any additional addons, connections will start dropping until the billing cycle resets. Let me know if you have any more questions. I hope that helps.
That sums it up. Thank you
[SOLVED] concurrent connections
Recommended threads
- Realtime not working for some tables
Hi, I've got an issue where I can setup a realtime connection to listen to some tables, but some not all. I have two tables `history` and `users`. Both can be ...
- SSR share session to client using custom...
Hi, so I was trying to get a hang of using SSR and using realtime updates in the same time which is done easiest if you have a custom domain in Appwrite and as ...
- Relationships and Realtime
Since now Relationship attributes are only returned when explicitly queried, how does this change reflect in Realtime? If a listener is listening to a row from ...