The coming-soon badges are about interop with traditional systems and higher level features we will add later.
The fundamentals are solved and you can build full multiplayer, local-first apps with it.
Does that make sense?
Which brings in even more questions. What is the performance of these multiplayer experiences? Can I have 1000+ users all connected to the same chat session? What about 10,000?
(these numbers might seem high, but they're what I'm expected to deliver in my day-job)
This lets us more easily prioritise features vs performance.
The commenter seems to know a lot about Jazz, so I took the opportunity to ask further questions.
Let me know if you'd like to know anything else.
I’m reminded of the quasi meme “You have designed an infinitely scalable service for 10 clients “
Especially within time (latency), monetary hosting cost, and accuracy constraints.
For example, an MMO town with 10,000 connected clients all viewing the same complex session state of all other users and entities in one town.
That’s a lot of room for error. Or am I missing something?
That scenario is complex to me and has remained complex to me despite my various times building it out for various products.
Free tier is 1GB of storage, and it goes up from there.
Its one thing to use this service on the basis of encryption claims - its another thing to have to clean up the mess from a forgotten API key being leaked somewhere... is there, therefore, a third party involved in an audit of Jazz?
Of course we will also do public audit(s) with security companies to make sure our cryptographic protocols are sound and implemented correctly.
But, it also has to be stated, there is no guarantee that you're using only the open source components you've declared, which is why an impartial audit by a third party would be necessary before this project can be used to build products in some industries.
Anyway, I see that you have other concerns, so no worries and thanks for the honest answer.