Need to Scale-Out Your Spring Application?

If you do, then you should come to my JavaOne session about Transparently Clustered Spring — A Runtime Solution for Java™ Technology and learn how to cluster your Spring application in minutes, with zero changes to application code.

The session (TS-3217) will be held on Tuesday, 05/16/2006, 02:00 PM - 03:00 PM and has the following abstract:

How do you scale a Spring application beyond a single node? How can you guarantee high-availability, eliminate single points of failure, and make sure that you meet your customer SLAs?

Historically speaking, clustering an application is not easy: it takes a significant amount of time and usually requires you to rewrite parts of your application. It also usually perturbs your domain model and breaks object identity.

But does it have to be like that?

In this talk, Jonas Bonér will walk you through how to cluster your Spring application, transparently and naturally, with no changes to your application code, using the Terracotta Spring Runtime.

The Terracotta Spring Runtime allows you to take an arbitrary Spring application, written for a single JVM™ machine, and cluster it to N nodes while preserving the exact same semantics.

For example:

• Life-cycle semantics and scope for Spring beans are preserved across the cluster - within the same logical ApplicationContext (singleton and session scoped beans).
• Spring’s local event mechanism in the ApplicationContext is turned into high-performance asynchronous, distributed and reliable events (messages), but still local within the same logical ApplicationContext.
• Clustered beans can be exported using Spring JMX support, which guarantees a single point of management and coherent view of all the JMX data in the cluster.
• Spring WebFlow’s web flows are transparently shared across the cluster.
• and more…

The session is backed up by several live demos.

See you there.

About this entry

You’re currently reading “Need to Scale-Out Your Spring Application?,” an entry on Jonas Bonér

Published:: 05.09.06 / 6am

Category:: Java, Distributed Computing

Anders 05.10.06 / 7am

Sounds interesting. Sadly I’m not going. Please do post slides if you can.

Cremenescu Florin 05.15.06 / 12pm

Hi Jonas,

The Terracota product seems very interesting. But as in the last month I worked in defining a scalable new architecture for my company, I wonder if we could use the product. For us, there are two important business goals : - diminish the number of business tests required to validate changes. More specifically, if some business parts are not changed they should not be tested, even the technical details of the implementation changed (for exemple the architectural framework evolved, some common libraries, or new services were added in some jars) - allow different levels of scalability to be specified on the business use cases.

The first goal is much more important than the second.

To achieve this, we plan to split our single EAR into several business domains EARs. Each EAR has his own copy of the domain model components (the architectural framework and the business components, but not the applicative parts). The user continues to benefit from services like SSO, caching, etc. Products like Terracota DSO, Terracota sessions could prove helpful to us. But, in order to achieve business tests independence, we plan to update architectural / business components of EARs at different speeds : so if a business case does not change, its EAR is not updated. Java serialization mechanisms (or XML transforms) allows to communicate different versions of the same class even if they are not the same. Is Terracota able to provide this mechanism : how it handles different versions of classes accros the cluster ?

Thank you in advance.

Florin

Jonas Bonér

Need to Scale-Out Your Spring Application?

About this entry

2 Comments

Have your say

About

Pages

Recently

Monthly Archives

Categories