Google Cloud Memorystore VS Confluent

I imagine that would work. I'd probably default to a redis https://cloud.google.com/memorystore because it feels more boring to me. Source: 5 months ago

I suggest you to use realtime database. It is cheaper than Memorystore (if you use in Google Cloud) and realtime database has a free tier. Source: 10 months ago

Memorystore is Google-hosted Redis/Memcached. You could set up a virtual machine and install Redis/Memcached yourself, but Memorystore eliminates that extra work and provides you with a well-working cache out of the box. Source: about 1 year ago

Memorystore is the managed cache service on GCP. https://cloud.google.com/memorystore. Source: over 1 year ago

Memorystore, the GCP managed service for cache, is not a service by itself, you need to choice the backend behind with Redis or memcached. These two kinds of configurations for Memorystore do not have the same model pricing. Memorystore for memcached is mostly based on Compute Engine model with pricing based on the number of nodes and vCPU + RAM per node. Even if the model pricing is nearly the same, the... - Source: dev.to / almost 2 years ago

We’re going to setup a Kafka cluster using confluent.io, create a producer and consumer as well as enhance our behavior driven tests to include the new interface. We’re going to update our helm chart so that the updates are seamless to Kubernetes and we’re going to leverage our observability stack to propagate the traces in the published messages. Source: about 2 years ago