Beyond REST: Building Data Services with XMPP?
XMPP and REST are two of my favorite tech areas, so I was glad to find this slideshow via Hacker News:
While the “Beyond REST” moniker seems propaganda-ish (REST is a great architectural paradigm), I found the XMPP information to be a good clarifying review of how one could integrate XMPP into their architecture.
I have been looking into XMPP in the past few days as a messaging solution for one of my current projects, and this slideshow couldn’t have come at a better time. I understand XMPP and have read the protocol documents several times, but for some reason this slideshow was the first time I really grokked the “integration process.”
XMPP and REST will both continue to be important protocols/architectures as the web evolves. They each have their place. I’m glad to see XMPP beginning to take hold in areas other than Jabber; hopefully they can continue to refine XMPP to heal some of its warts.1 I foresee XMPP becoming the de-facto standard for the “push” web as time passes, much as HTTP forms the foundation of the “pull” web.
-
I won’t detail here, but people have raised concerns about its overuse of XML namespaces, the plethora of extension documents (in comparison to actual implementations thereof), verbosity of presence stanzas, etc. ↩
