- Introduction
- How DSO Clustering Works
- Platform Concepts
- Hello Clustered World
- Setup and Configuration
- Planning for a Clustered App
- Configuring Terracotta DSO
- Configuration Reference
- Installation
- APIs
- Using Annotations
- Cluster Events
- Data Locality Methods
- Distributed Cache
- Clustered Async Data Processing
- Tool Guides
- Developer Console
- Operations Center
- tim-get (TIM Management Tool)
- Platform Statistics Recorder
- Eclipse Plugin
- Sessions Configurator
- Clustering Spring Webapp with Sessions Configurator
- Maven
- JMX
- Testing, Tuning, and Deployment
- Top 5 Tuning Tips
- Testing a Clustered App
- Tuning a Clustered App
- Deployment Guide
- Operations Guide
- FAQs and Troubleshooting
- General FAQ
- DSO Technical FAQ
- Troubleshooting Guide
- Gotchas
- Non-portable Classes
- Reference
- Migrating From DSO
- Concept and Architecture Guide
- Examinator Reference Application
- Clustered Data Structures Guide
- Integrating Terracotta DSO
- Clustering Spring Framework
- Integration Modules Manual
- AspectWerkz Pattern Language
- Glossary
|
Release: 3.6
Publish Date: November, 2011 |
This example shows how to cluster a Map using Terracotta. Note that the map used in this example is a java.util.HashMap. As in
standard Java, the HashMap structure in Terracotta is not automatically locked, and requires external synchronization.
For an automatically locked Map, use for example java.util.concurrent.ConcurrentHashMa. For production code, the Terracotta Toolkit provides a fully locked, highly concurrent, automatically distributed (shared) map.
The following items are required to run the HashMap example:
How to run
A Terracotta Server instance is always required to run Terracotta. dso-java(.sh|.bat) is a wrapper script that adds Terracotta to standard java. After the Terracotta server is running, start the two nodes:
Node 1:
Node 2: