[ https://issues.jboss.org/browse/ISPN-8469?page=com.atlassian.jira.plugin.... ] John Brier commented on ISPN-8469: ---------------------------------- I see your point. The original draft descriptions used "persistence" and "without persistence" to distinguish each other: "In this image, JBoss Data Grid is configured as a shared memory service with persistence. That means any data stored by the service will be preserved across restarts. ""In this service, JBoss Data Grid is configured as an in-memory caching service without persistence. Data in the cache will be lost if the service is stopped or restarted, and therefore, it should not be used as a permanent store for data." I think it meant persistence *across the cluster/service*, which does make sense. But maybe that is a non-traditional usage of the term we shouldn't use. I replaced persistence with fault-tolerance in the draft below. {quote}JBoss Data Grid is a high performance, linearly scalable, key/value data grid solution. It provides many features to serve a variety of use cases. In this image, JBoss Data Grid is configured as a shared memory service with fault-tolerance. That means any data stored by the service will be preserved across restarts. fault-tolerance is achieved by replicating data across multiple nodes. The data is copied to a specific number of nodes in the cluster using the "owners" setting. This ensures that, in the case of failure, the grid will not lose data as long as the number of failed nodes is less than the number of copies (owners). This also works when nodes are shutdown or restarted manually{quote} We can shorten it later if needed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)