# Replicated A replicated cache can exist in multiple application server machines and their contents will be replicated, meaning all caches will contain all the data elements. This type of topology is beneficial as it allows for all members in the application cluster to have availability to its elements. However, there are also some drawbacks due to the amount of chatter and synchronization that must exist in order for all data or cache nodes to have the same data fresh. This approach will provide better scalability and redundancy as you are not limited to one single point of failure. This replicated cache can be in-process or out-process depending on the caching engine you are using. ![](/files/-LA-Uq1Fdp5h9-S8ndKn) ## Benefits: * Better scalability * Cache data can survive server restarts if one goes down, better redundancy * Better cache availability through redundancy * Higher storage availability * Ideal for few application servers ## Cons: * A little bit harder to configure and setup * High serialization and network communication costs * Could need load balancing * Can scale on small amounts only --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://cachebox.ortusbooks.com/7.x-1/for-the-geeks/cache-topologies/replicated.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.