Thanks so much. 1. I appreciate the C++ and Node choice sounds like a strange idea at first, but allowed us to significantly speed up development and benefit f

Thanks so much. 1. I appreciate the C++ and Node choice sounds like a strange idea at first, but allowed us to significantly speed up development and benefit from the rich NodeJS integration ecosystem without sacrificing performance. We wrap both aspects into a single, pre-compiled executable with further performance optimizations. There's also C++ client SDK which we're currently extending (https://github.com/deepstreamIO/deepstream.io-client-cpp https://github.com/deepstreamIO/deepstream.io-client-cpp). 2. The C++ client is designed from the ground up as a foundation for a Python and Go client via SWIG wrapping - so a Python client is on the very immediate roadmap. Crossbar and the WAMP standard provide pub/sub and request/response which deepstreamHub offers as well, but deepstream's core is a realtime datastore for stateful objects that are persisted and synced (think Liberator records). 3. Yes, it's called listening. You register a RegExp pattern and get informed whenever the first client subscribes or the last client unsubscribes from a record or event matching that pattern. This allows for the creation of active data provider that send data only when needed. Deepstream offers some additional functionality like provider state and failover as well as the ability to add more provider on the fly and loadbalance requests between them. 4. Yes - but due to the nature of these I'm afraid I can't publicly disclose them. Happy to discuss on wolfram.hempel@deepstreamhub.com