Differences between BlazeDS web messaging and the messaging service in LiveCycle Data Services

I've decided to make this post because recently I'm receiving a lot of questions from our clients about how BlazeDS web messaging differs from the messaging service in LiveCycle Data
Services ES. The answer is pretty simple and well explained by Adobe on the FAQ page (you can read it at the end of this post). But a point of confusion is probably the Adobe LiveCycle Data Services Community Edition licensing against the standard Adobe LiveCycle Data Services and BlazeDS.

The Adobe LiveCycle Data Services Community Edition offers as a subscription service that includes certified builds of BlazeDS along with Adobe support (you can choose from Bronze or Gold support).

How does BlazeDS web messaging differ from the messaging service in LiveCycle Data
Services ES?

BlazeDS’s web messaging, using COMET-style long polling or the new HTTP streaming channel thatestablishes a persistent connection between client and server for true data push, is capable ofhandling roughly 100-200 users per CPU, depending on many different factors. Scalability isconstrained by the current servlet specification where each persistent connection utilizes a servletthread. In contrast, LiveCycle Data Services ES provides a dedicated messaging service that runs ona separate process and is capable of supporting thousands of users per CPU, bypassing the servletscalability limitation and reducing the amount of memory required. The dedicated messageservice also supports the RTMP protocol, which offers more advanced two-way communication notsupported by the HTTP protocol.For applications that require massive scalability and performance, such as real-time stock trading,most customers will require the more specialized features of LiveCycle Data Services ES.