Thanks, @ashitvora! We use a scaling model where each document has its own process, which allows us to horizontally scale out the servers. For the use cases we see most we don't hit any sort of connection limits, but if you have a use case with a high connection count I'd be glad to talk about it with you! Conflict resolution is handled by the Yjs CRDT (conflict-free replicated data types) library. For lists and text, if multiple people insert text Yjs will attempt to preserve both in a reasonable way. For maps, it's last-write-wins like you describe.

@ihuzaifashoukat thanks! The feature I'm most proud of is that there's no lock in -- if you deploy with us and want to switch to self-hosting, you can, and vice-versa. My favorite little feature is that if you have node.js installed, you can run a server just by running "npx y-sweet serve" -- even though it's a Rust server, it will automatically download and run the correct pre-compiled binary.