What in-client caching options work well with Cassandra and Java?

Question

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 don't think you should presume that hitting Cassandra for this data will be too slow. If the data you're accessing is either fresh or hot, it'll always be in memory anyhow and all you'll do is waste more memory by caching it again. You should experiment and test rather than presume. — Nick Bastin, Jun 20 '10 at 18:21

Schildmeijer · Answer 1 · 2010-06-18T22:51:20.307

1

I would start by investigating if the cassandra key (avoid index scan) and/or row cache (avoid sstable lookup) is sufficient enough.

detailed information: http://wiki.apache.org/cassandra/API

edited Jun 18 '10 at 22:51

answered Jun 18 '10 at 14:33

Schildmeijer

20,702
12
62
79

Are these cached in the client? Can you give me a reference to more detailed information on it? – sanity Jun 18 '10 at 14:36
1

thats pure server side caching – Schildmeijer Jun 18 '10 at 22:50

score 0 · Accepted Answer · answered Jun 18 '10 at 14:24

0

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).

answered Jun 18 '10 at 14:24

Peter Tillemans

34,983
11
83
114

What in-client caching options work well with Cassandra and Java?

2 Answers2

Linked