Integrations - Spring |
rate-4948083-70553
| Article Rating? |
|
|
|
| Product Type |
Container |
| Versions Supported |
1.2.4, 2.0 (up to 2.0.5), Web Flow 1.0, Events |
| Module Status |
Included with Terracotta kit |
| Module Availability - Released (latest) |
Not Applicable |
| Module Availability - SNAPSHOT (latest) |
Not Applicable |
| Download with Kit |
See latest Terracotta Kit |
| Additional Documentation |
Spring Quick Start Guide |
 | Terracotta does not support Spring 2.5 at the time of this writing. If you would like to see support for Spring 2.5, please:
|
Introduction
Built on top of Terracotta Distributed Shared Objects (DSO) technology, Terracotta for Spring is a transparent runtime for Spring-based applications that provides high-availability and high-performance clustering for your Spring applications—without requiring changes to the application code. The core features of this runtime include clustering of Spring-managed components (singleton and scope-bound), as well as events.
With Terracotta for Spring, developers can create single-node Spring applications as usual. They define which Spring application contexts to cluster in the Terracotta configuration file. Terracotta for Spring clusters the target applications automatically and transparently, with the same semantics across the cluster as on the single node.
Terracotta for Spring does not require access to the source code. Applications are transparently instrumented at load time, based on a declarative XML configuration.
Additionally, Terracotta for Spring does not require that classes implement Serializable, Externalizable, or other interfaces or annotations because no serialization (or flattening the entire object graph) takes place. Instead, only changed data is sent over the network.
Dependencies
For detailed version information, see Platform Support.
Implementation
To implement Terracotta for Spring, edit the file config-examples/tc-config-spring.xml as described in the Spring Quick Start Guide. When you are ready to run the Terracotta server, start it with tc-config-spring.xml in place of tc-config.xml.
Known Issues
None.