What is Deepstream.io -
i've been reading deepstream & seems awesome solution real-time applications. confused however, in deepstream's actual role is.
the documentation core features (data-sync, records, auth, permissions, events, rpc, ...) written, except low level. think through high-level explantation of deepstream should used missing.
my question is:
- is deepstream full-fledged/stand-alone backend framework real-time based application?
- or deepstream server platform used directing (auth,routing,caching, load balancing) communication microservices (and/or principal application layers) clients?
- or quite different?
would appreciate detailed explanation of how developers should distinguish deepstream , possibly direction on how deepstream should incorporated in our applications.
thanks.
deepstream standalone server that’s installed e.g. nginx or database. it’s available via yum/apt linux distros windows , macos executable.
a deepstream server accepts client connections via tcp , websocket. clients can connect via sdks available js/node & java/android , partially/soon available ios(obj c/swift), python , .net.
deepstream provides 3 core concepts:
data-sync: stateful , persistent json objects can manipulated in whole or in parts , synchronized across connected clients
pub-sub: many-to-many messaging based on subscriptions topics
request-response: question/answer workflows
the server configurable , uses permission files validate incoming messages, doesn’t hold logic other that. logic provided “clients” can backend processes end-users. deepstream provides numerous features such listening , active subscriptions hook users request , provide/transform data accordingly integrate , retrieve data third party components or apis.
this makes deepstream useful both realtime server mobile/browser , desktop clients backbone microservice architecture
deepstream can optionally integrated 3 types of systems:
- databases can used long-term data storage , querying
- caches can used fast short-term data access
- message busses can used multiple deepstream nodes communicate each other
connectors available many popular systems, e.g. rethinkdb, mongodb, redis, amqp, kafka or elasticsearch , can written yourself. animation aims provide impression of how deepstream interacts other systems
if no external system specified, deepstream run single node , store data in internal memory, won't persist disk.
Comments
Post a Comment