Software Developer, Writer and Author of How to build a serverless app platform on Kubernetes - https://books.pmbanugo.me/serverless-app-platform
Building https://cronatlas.com
I believe the 100 connections is specifically for the presence channels. I don't think that's a constraint on other uses of the product. But we'll get more of the Pusher folks in here to clarify anything.
Correct - for the submissions to qualify the projects need to use Channels.
Of course, you are free to use any other APIs or services as well - and that includes Pusher products :)
And regarding the limits in the free/sandbox tier:
the limit is 100 concurrent connections. You can have more users, but not connected at the same time. You can find more info here: support.pusher.com/hc/en-us/articl...
Sounds cool.
So the constraints are using the channels API and not the chat/editor stuff.
And iff I got this correctly after reading the docs, the constraints of this API are:
10 connections * 1 msg published == 10 msg deliveredI think 10 connections * 1 message = 11 messages in total
Ah, right.
I believe the 100 connections is specifically for the presence channels. I don't think that's a constraint on other uses of the product. But we'll get more of the Pusher folks in here to clarify anything.
Correct - for the submissions to qualify the projects need to use Channels.
Of course, you are free to use any other APIs or services as well - and that includes Pusher products :)
And regarding the limits in the free/sandbox tier:
the limit is 100 concurrent connections. You can have more users, but not connected at the same time. You can find more info here: support.pusher.com/hc/en-us/articl...
message counts are as Peter Mbanugo described, you can read more about it here: support.pusher.com/hc/en-us/articl...
The rest is correct