Evgeny Poberezkin
5b39f51203
* example websockets server * example of ws client * type class TConnection for generic TCP/WebSockets implementation * support WebSockets transport * rename TConnection methods * revert runClient to not need transport arg * pass the list of ports and transports via SMP server config * remove TypeApplications * s/Transport/TProxy/, s/TConnection/Transport/ * fix server with multiple transports, make SMP client use WS transport with port 80 (TODO fallback to WS)
SimpleXMQ
Message broker for unidirectional (simplex) queues
SimpleXMQ is a message broker for managing message queues and sending messages over public network. It consists of SMP server, SMP client library and SMP agent that implement SMP protocol for client-server communication and SMP agent protocol to manage duplex connections via simplex queues on multiple SMP servers.
SMP protocol is inspired by Redis serialization protocol, but it is much simpler - it currently has only 8 client commands and 6 server responses.
SimpleXMQ is implemented in Haskell - it benefits from robust software transactional memory (STM) and concurrency primitives that Haskell provides.
SimpleXMQ roadmap
- Streams - high performance message queues. See Streams RFC for details.
- "Small" connection groups, when each message will be sent by the SMP agent to multiple connections with a single client command. See Groups RFC for details.
- SMP agents cluster to share connections and message management by multiple agents (for example, it would enable multi-device use for simplex-chat).
- SMP queue redundancy and rotation in SMP agent duplex connections.
- "Large" groups design and implementation.
Components
SMP server
SMP server can be run on any Linux distribution without any dependencies. It uses in-memory persistence with an optional append-only log of created queues that allows to re-start the server without losing the connections. This log is compacted on every server restart, permanently removing suspended and removed queues.
To enable the queue logging, uncomment enable: on option in smp-server.ini configuration file that is created the first time the server is started.
On the first start the server generates an RSA key pair for encrypted transport handshake and outputs hash of the public key every time it runs - this hash should be used as part of the server address: <hostname>:5223#<key hash>.
SMP server implements SMP protocol.
SMP client library
SMP client is a Haskell library to connect to SMP servers that allows to:
- execute commands with a functional API.
- receive messages and other notifications via STM queue.
- automatically send keep-alive commands.
SMP agent
SMP agent library can be used to run SMP agent as part of another application and to communicate with the agent via STM queues, without serializing and parsing commands and responses.
Haskell type ACommand represents SMP agent protocol to communicate via STM queues.
See simplex-chat terminal UI for the example of integrating SMP agent into another application.
SMP agent executable can be used to run a standalone SMP agent process that implements plaintext SMP agent protocol via TCP port 5224, so it can be used via telnet. It can be deployed in private networks to share access to the connections between multiple applications and services.
Using SMP server and SMP agent
You can either run SMP server locally or try local SMP agent with the deployed demo server:
smp1.simplex.im:5223#pLdiGvm0jD1CMblnov6Edd/391OrYsShw+RgdfR0ChA=
It's the easiest to try SMP agent via a prototype simplex-chat terminal UI.
SMP server design
SMP agent design
