Introduction to RestMS
Translation of the original in Catalan. Read it in: CatalàCastellano
is a messaging protocol not only aimed at keeping conversations between users but also at being used as an
system between different applications. Even so nothing is perfect and AMQP, more oriented to the second function than to the first, is shaping up as a corporate standard far more powerful and efficient than XMPP in several aspects. But AMQP suffers from being quite inaccessible because it is not trivial to understand and use.
In this whole world of messaging between applications there is another protocol that is not so well known but that claims to have the best of XMPP and of
:
. In fact, RestMS is really a simplification of AMQP that uses
as its transport system.
It is an open standard, with a fairly solid Open Source implementation. This standard gives us:
- message routing system
- queue models
- easy to extend its semantics
- simple, because it is precise and small
- secure, it uses the standard HTTP security systems
- scalable, because it uses servers, caches, proxies, etc. from the HTTP world
- it solves the 'polling vs events' dichotomy using long-polling, just like BOSH
- in principle it does not have a presence system, although it could easily be set up
- it can encode the data in XML or JSON during transport
- portable across different operating systems
- it offers interoperability between different programming languages
For all this RestMS is shaping up as an interesting alternative for some environments, providing a simple and powerful solution in many aspects. Although with the theory in hand, I find it quite a lot slower than AMQP. In fact, ever since I saw how an AMQP system was used to do load balancing in video applications using GStreamer for a 'fast and dirty' test I was impressed.
- Article based on the information from: RestMS presentation
