1) We are not using persistence at all in beta, this is something we are working towards
2) Scaling of basic tier will result in a full cache flush and will cause downtime during the scaling process.
3) That's correct
4) Yes we will be making Import-Export of RDB very soon
Persistence is a key feature of Redis, it isn't just a fancy memcached. This severely limits the applicability of this offering.
Can you speak to what kind of durability you expect to achieve once persistence is in place? Is it reasonable to treat this as a durable datastore and simply have a disaster recovery plan in place? Or should applications be prepared to handle occasional minor data loss?
Maybe don’t advertise it as a “data store” then.
> and features like persistence, replication and pub-sub.
(Customer testimonial) > We have used Redis on everything from storing asynchronous task queues for tens of thousands of CPUs to a centralized persisted key-value pair store for the feature vectors output by our ML models
Additionally, “persistence” isn’t mentioned at all in the “Coming soon to Cloud Memorystore” section.
I’m not trying to be a pedant, I just think it’s dangerous that it’s not made abundantly clear that there is no persistence.
I read it differently. When they say full cache flush doesn't that imply full database flush, I was thinking all data gets wiped on scaling operation.
1) Yes, they're using Redis persistence (RDB, AOF, or a Google-written persistence layer, it's not specified).
2) Basic Tier scales by tearing down the smaller Redis instance and migrating the data (???) to a larger instance. This causes downtime, but not lost data.
3) Standard Tier migrates using replication during scaling, so there's little downtime but if data is in flight at cutover, it could be lost.
4) And "coming soon" you can migrate data in and out of Cloud Memorystore by importing and exporting RDB files.