yer for a
>> Cassandra back-end”), and I’m aware of at least one large private
>> enterprise that does this.
>>
>>
>>
>> *From:* Dorian Hoxha [mailto:dorian.ho...@gmail.com]
>> *Sent:* Friday, October 07, 2016 3:48 AM
>> *To:* user@cassandra.apache.or
mail.com]
> *Sent:* Friday, October 07, 2016 3:48 AM
> *To:* user@cassandra.apache.org
> *Subject:* Re: Rationale for using Hazelcast in front of Cassandra?
>
>
>
> Primary-key select is pretty fast in rdbms too and they also have caches.
> By "close to" you mean in latency ?
>
Cassandra
back-end”), and I’m aware of at least one large private enterprise that does
this.
From: Dorian Hoxha [mailto:dorian.ho...@gmail.com]
Sent: Friday, October 07, 2016 3:48 AM
To: user@cassandra.apache.org
Subject: Re: Rationale for using Hazelcast in front of Cassandra?
Primary-key select
put a cache in front of a cache?
>
>
>
> *From:* Dorian Hoxha [mailto:dorian.ho...@gmail.com]
> *Sent:* Thursday, October 06, 2016 2:52 PM
> *To:* user@cassandra.apache.org
> *Subject:* Re: Rationale for using Hazelcast in front of Cassandra?
>
>
>
> Maybe when you can
?
From: Dorian Hoxha [mailto:dorian.ho...@gmail.com]
Sent: Thursday, October 06, 2016 2:52 PM
To: user@cassandra.apache.org
Subject: Re: Rationale for using Hazelcast in front of Cassandra?
Maybe when you can have very hot keys that can give trouble to your
3(replication) cassandra nodes
Maybe when you can have very hot keys that can give trouble to your
3(replication) cassandra nodes ?
Example: why does facebook use memcache ? They certainly have things
distributed on thousands of servers.
On Thu, Oct 6, 2016 at 11:40 PM, KARR, DAVID wrote:
> I've seen use cases that briefly de
I've seen use cases that briefly describe using Hazelcast as a "front-end" for
Cassandra, perhaps as a cache. This seems counterintuitive to me. Can someone
describe to me when this kind of architecture might make sense?
