- XML standard encoding: sucks (in protocols, ok in blogging)
- XML data model: rocks
I’ve expressed my feelings for binary XML in the past, at least twice. XML is perfectly fine more often than not, and usually, if you believe you have a problem that you can solve by replacing XML with something “better” you’ll end up with two problems. But anyway …
Mike Herrick thinks I’m “temporarily a binary message bigot”.
Damn. Let me try to make myself clear: Believe it or not, message-oriented middleware works very well in its domain. Sadly, while there is some portability due to JMS, there is no interoperability. Because of this, an efficient protocol that addresses this (AMQP) is a perfectly valid idea. Of course this does not mean that suddenly, AMQP becomes an alternative to an Internet-scale protocol such as XMPP; but the same is true vice versa, unless looser coupling has higher priority than performance for your problem space.
I’m more and more convinced that most company-internal integration/communication scenarios share the exact same problems as cross-company, Internet-scale scenarios. In other words, what works on the Internet is very likely going to be the “right” solution for your company. But “most” does not mean “everything”, and I’ll happily consider AMQP a useful criterion for evaluating MOM solutions if and when it becomes widespread enough.