tags:

views:

20

answers:

0
Q: 

Terracotta client crush

Hi, One thing i didn't understnad in the terracotta framework. According to the documentation each object is kept in one terracotta client instance. What happened if this client crush? is the data lost?

related questions

distributed caching on mono
Terracotta for Python world?
How does NetworkInterface work within a cluster?
Does Terracotta make JMS an unneeded layer?
DistributedMap as cache clustered with Terracotta
Single point of access for failover
Durable queue configuration in Terracotta
Teracotta and Hibernate Search
Clustering COMET using Terracotta
How does Terracotta work in this situation?
Terracotta Performance and Tips
Terracotta - Cannot cast to com.tc.object.bytecode.TransparentAccess
Querying Terracotta
Regarding Terracotta and Servlets/ Shared Threads.
Terracotta + Compass = Hibernate + HSQLDB + JMS?
Would you consider Terracotta to be a mature product?
What would you recommend for a large-scale Java data grid technology: Terracotta, GigaSpaces, Coherence, etc?
Terracotta as data layer
On using Terracotta as a persistence solution.
Any experience using Terracotta open source?
Are "dirty reads" safe to use in Terracotta?
Can I use Terracotta to scale a RAM-intensive application?
Distributed Concurrency Control
experience with java clustering ?
Looking for terracotta examples