We already use BlazeDS in a Spring/Hibernate Environment. After some optimizations because of serialization/lazy loading issues we are quite happy with the implementation. But, we did not do load tests in the past.
I read some weeks ago that you shouldn't use BlazeDS if you need a highly scalable solution and use Lifecycle instead. What do you think when we should think about a change?
BlazeDS or LCDS depends on your application requirements, if you are using traditional http, webservice or amf remoting request and response model then there is no difference between LCDS and BlazeDS because you are still restricted by the your OS, hardware and bandwidth capacity for processing number of requests per second.
Use of LCDS depends of your application requirements e.g. if you are looking for Real Time Messaging Protocol (RTMP), Reliable communications, Data conflict resolution and synchronization, data push and Enterprise document integration such as PDF capabilities then LCDS would be the choice.