Spring and failover

[JeanLouis Marechaux]

My understanding, mostly based on the discussions with you today guys , is that Spring is good (I'm trying to demonstrate that I'm not a string opponent here :-) )

But what if I need high availability. It sound like I still need a J2EE application server for failover capabilities. Is that true ??

Besides, from Spring documentation I can read :
Spring also provides an access layer and abstraction layer for Enterprise JavaBeans, enabling you to reuse your existing POJOs and wrap them in Stateless Session Beans, for use in scalable failsafe web applications, that might need declarative security.

for use in scalable failsafe web applications.... wht's behind this ?? scaring, huh ?

[Lasse Koskela]

As long as you deploy on a J2EE application server that supports failover for web applications, Spring is as good a choice as Struts+EJB or WebWork+JDO or whatever. At least that's how I see it -- being a question of replicating the HttpSession within a cluster.

[Karthik Guru]

I think this is turning out to be a nice discussion. Thanks esp to Jean for questioning Spring.

Originally posted by Lasse Koskela:
At least that's how I see it -- being a question of replicating the HttpSession within a cluster.

So a Clustered Web Container that offers HttpSession replication should be fine?. Jean would like to know your thoughts on clustering requirements.

[Karthik Guru]

Hello Authors,

Would you mind sharing your thoughts on this topic?

[Rob Harrop]

To a certain degree you are correct - if you want failover then use a container that supports it. However, bear in mind that often the simplest way of doing failover is to use some kind of hardware clustering kit with Tomcat sat behind it.

I *think* that you can also achieve the same thing with Apache as the load balancer/fail-over manager.

Spring itself has no code to support application failover, but it will happily work alongside J2EE failover capabilities.

Rob