yup, that's not too far off. It also gives you Pub/Sub and Request/Response though. Also Firebase uses one huge data-structure for data-sync whereas deepstream breaks data down into smaller objects called "records" with individual lifecycles

Huh. I visited your site and reading the tag line "a fast, secure and scalable websocket & tcp server", I assumed it was just a socket server and had no idea it was actually a data-store.

Yeah I mostly understood that from the example.

You really need to make the explanation clearer ^^

Very much agree. Would you have any recommendation?

I would show what it does step by step: one box with data-sync, one with real-time data sharing, etc... with an animation for each.

Your animation "built for a new generation of apps" is awesome but it doesn't not show clearly what role deepstream plays in it.

I don't think it is possible to explain everything clearly in one sentence so I wouldn't start with a tagline like that.

+1 something like this is defintley needed

I know the question wasn't directed to me, but the animation on the 'Cluster Messaging'[1] page really helped me understand.

[1] https://deepstream.io/tutorials/core/cluster-messaging/