什么客户端缓存选项适合Cassandra和Java？ [英] What in-client caching options work well with Cassandra and Java?

问题描述

我目前正在架构一个必须能够处理每秒数万次写入的系统。我已经决定使用Apache Cassandra作为持久化层，并且将使用Java作为应用程序层，但是在某些情况下，我需要快速访问数据，以便在几秒钟内获取任何更改。 / p>

点击Cassandra每次我需要检查这些数据的变化会太慢，这意味着我需要使用某种应用层缓存。

为了确保缓存数据保持最新，理想情况下它将支持某种基于多播的缓存失效。

我使用了 ehcache 和它工作真的很好。很好地配置外的应用程序，它支持多播无效（和基于磁盘的持久性，我需要的无效）。

I'm currently architecting a system that must be capable of dealing with tens of thousands of writes per second. I am more-or-less settled on using Apache Cassandra for the persistence layer, and will be using Java for the application layer, but there are situations where I need to quickly access data in a way that picks up any changes within seconds.

Hitting Cassandra every single time I need to check this data for changes will be too slow, which means I need to use some kind of application layer caching.

To ensure that the cached data remains current, ideally it would support some kind of multicast-based cache invalidation.

What are my options?

解决方案

I have used ehcache and it worked really nice. Nicely configurable outside the app and it supports multicast invalidation (and disk based persistence which I needed more than the invalidation).

这篇关于什么客户端缓存选项适合Cassandra和Java？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！