This article, by Ryan Knight, compares two similar products: Adobe’s LiveCycle Data Services (LCDS) and Open Source Blaze Data Services. The comparison is necessary to know the differences between the two products in order to choose the right one for a certain situation.
Read: Blaze Data Services or LiveCycle Data Services?
Since LCDS comes in four editions, there are five products in total:
- Blaze Data Services - Free and Open Source edition
- LiveCycle Data Services Community Edition - A supported version of Blaze DS
- LiveCycle Data Service Single-CPU License - A free version of the commercial edition with the additional features but limited to a single CPU
- LiveCycle Data Services - The paid version of the commercial edition with support
- LiveCycle Data Services Enterprise Suite – The paid version plus PDF Generation, Forms, and Digital Signatures, and others.
Choosing one of them needs to take into consideration the following most important factors: the need for support, the need for data management services, and the need for opening hundreds of concurrent connections. Ryan explains which product to choose considering those needs.
Community comments
ALDS
by Christopher Brind,
i like the rails
by withyou gakaki,
Free course on BlazeDS and Flex/AIR
by Duane Nickull,
Theoretically it's right, but...
by Yakov Fain,
ALDS
by Christopher Brind,
Your message is awaiting moderation. Thank you for participating in the discussion.
The abbreviation commonly used is actually LCDS, which is used in the main article also.
i like the rails
by withyou gakaki,
Your message is awaiting moderation. Thank you for participating in the discussion.
rubyamf and phpamf is well
not java platform
Free course on BlazeDS and Flex/AIR
by Duane Nickull,
Your message is awaiting moderation. Thank you for participating in the discussion.
If anyone is interested in learning how to build 5-6 projects in Flex or AIR to talk to a custom build of BlazeDS with an Apache Axis SOAP stack (v 1.4), you can download it from www.web2open.org/courses.html. This course is self paced and you are free to take the materials, code samples and teach them in your own 'hood. Ciao!
Theoretically it's right, but...
by Yakov Fain,
Your message is awaiting moderation. Thank you for participating in the discussion.
Theoretically your conclusions regarding the "useless NIO" may be right if you live in the world of servers with unlimited power CPU/Memory and when each Java thread won't take a specific amount of resources in a JVM with a limited heap size.
Our company, Farata Systems, did some real performance tests hitting BlazeDS hard emulating thousands user requests with a PROFESSIONAL stress test software. This test put the Tomcat/BlazeDS down reaching 800 users. After that, we've created our own solution that works with Jetty server and can be stable with at least 5K users hitting Jetty/BlazeDS. Here's a video recording of this stress test:myflex.org//demos/JettyBlazeDS/JettyBlazeDSload...
Jetty's suspend/resume thread architecture was supposed to be used as a base for Servlet 3.0 spec, but because of some weird reason it didn't happen, so our solution works with Jetty only at this time.