Regarding the 5000 users limit per room in LCCS:
Is it an automatic limitation, or is there a way to over pass this limit?
And why do you apply this limit?
In a previous discussion, i was answered: "ideally if you want to build a really scalable app, you should distribute connections in multiple rooms"
But if i have multiple chat rooms, the user will have to endure the connection time (not so short) every time he changes chat room. When i use a single LCCS room for all my chat discussions, i can limit to only one connection time for the whole App, which is much better user experience.
And if i need a global chat room available for all logged in users?
Moreover, i also use the global room connection between all users to keep some common informations updated live, especially for example to keep the online users, and the online state of chat rooms hosts. How can i do differently without connecting every user at same time?
If i can't get over this 5000 limitation, what solution Adobe has to offer, to get the great LCCS features, whitout limitations? A FMS server? but i'll have to recreate all LCCS services myself?
To be clear: I need a scalable realtime service between all users of my app (not only a restricted chat room at a time). How can i do?
Yes, the 5000 users limit per room is configurable and we can configure that on account to account basis depending on your requirement. This is just the default standard value.
Just to clarify, while the limit is configurable we can't really update every room on request. The limit is there so that one room can't take over a server and penalize other rooms.
Depending on your contract and the characterists of your application we may or may not able to increase the limit for your rooms. Anyway, if you want to discuss more details please send an email to email@example.com.
If i need it i'll send mail to this adress.
But I don't understand why breaking those limits in my room can "penalize other rooms" when LCCS use a CLOUD architecture?
And you say "Depending on your contract", but the LCCS way to subscribe, is standard and i never saw a way to change some caracteristics of contract.
Once a room has started is pegged to on FMS server until it ends (and while we have a pool of FMS servers they are not unlimited) so a room with thousand of user will use more resources (sockets and memory) than other rooms on the same server.
The "basic" paid account is a pay per use contract: you declare how much you are willing to pay per month as maximum but you get charged only for what you use. For this contract we don't offer much customizations.
But we do offer other contracts with a peak concurrent user model where you pay for an estimated number of concurrent users. For these type of contracts you can potentially negotiate some account customizations.
Sent from my iPhone
Thanks for the detailed answer.
I should read more about those customizable LCCS contracts, but are those contracts still rulled by the "you pay what you use" basis?
And about the servers. You say the FMS servers are not unlimited. But is the LCCS service not based on cloud infrastructure?
I thought cloud computing, was able to create virtually unlimited servers sizes, which would be perfect for the scalability of FMS heavy uses.
Am i wrong about cloud computing?
is LCCS not totally based on cloud instratucture?
can i get over those limitations if i use my own FMS server on Amazon EC2 recently announced? (or another Adobe product?) but in this case, ill have to create my own LCCS implementation, from scratch, which is quite some work to do
I am a bit disappointed from those limitations (even over 5000) because i love the LCCS business model and powerfull fonctionnalities.
It is so great to say: "you pay only when you have success" (because with a good business model of a web project earnings growth along with success), and you can have a success from 2 users to potentially millions without worries about technical background and its price.
For contract/architecture questions, i'd recommend that you contact the team directly: lccs(at)adobe(dot)com.
You'll get a timely answer there as well.
The forums are best used for coding questions and/or to report bugs found in the SDK.
LCCS Quality Engineering