A chat app using streams
Demonstrates usage of
Multi channel MDM allows you to create real time communication channels that arbitary clients can pipe in and out from.
Backing the channel in redis allows you to distribute this.
boot gives you access to a MDM object on the client from which you can open arbitary named streams.
boot itself handles reconnection logic for you like magic. Never worry about those pesky internet connections again
On the server boot allows any browser to open a connection as a stream. You then have a single handler on which you can take any other stream and pipe it into it.
You can attach an uri to a stream from MDM as meta data. This basically allows you to write a router for all your stream connections
No more pesky HTTP handlers. Just deal with streams and pipe all your IO!
Why expose some weird View or Model object when your UI widget can just be a stream.
If the UI wants to report that some event or input happend it emits data like a readable stream, if your UI wants to render something, it is written to like a writable stream.
Have mountie handle load balancing for you.
Split your application up into small chunks by the public HTTP API. Then use seaport to have these processes talk to each other.
Take advantage of the fact that mountie picks a random process if multiple match so you can spawn as many as you want for all your scaling needs
- Raynos