TBH, this sounds to me like a very expensive (in terms of effort) way to deal
with whatever Kafka unreliability you’re having. We have lots of both Kafka and
Cassandra clusters under management and I have no doubt that Kafka is capable
of being as reliable as Cassandra (and both are capable
Hi Gowtham,
On the face of it, it sounds like you are planning to use Cassandra for
a queue-like application, which is a well documented anti-pattern. If
that's not the case, can you please show the table schema and some
example queries?
Cheers,
Bowen
On 17/02/2024 08:44, Gowtham S wrote:
Thanks for your suggestion
Thanks and regards,
Gowtham S
On Sat, 17 Feb 2024 at 14:58, CPC wrote:
> hi,
>
> We implemented same strategy in one of our customers. Since 2016 we had
> one downtime in one DC because of high temperature(whole physical DC
> shutdown).
>
> With that approach I
hi,
We implemented same strategy in one of our customers. Since 2016 we had one
downtime in one DC because of high temperature(whole physical DC shutdown).
With that approach I assume you will use Cassandra as a queue. You have to
be careful about modeling and should use multiple partitions may
Dear Cassandra Community,
I am reaching out to seek your valuable feedback and insights on a proposed
solution we are considering for managing Kafka outages using Cassandra.
At our organization, we heavily rely on Kafka for real-time data processing
and messaging. However, like any technology,
