Hacker News Reader

Hacker News

Comment by nodesocket | Hacker News Reader

Full thread

nodesocket

Great. Does this support persisting to disk RDB[1] or AOF[2]?

Pricing seems reasonable?

1GB of Redis data is $0.049 per GB hour. 730 hours in a month = $0.049 * 1 * 730 = $35.77/mo.

5GB of Redis data is $0.027 per GB hour. 730 hours in a month = $0.027 * 5 * 730 = $98.55/mo.

[1][2] https://redis.io/topics/persistence

View on HN

Those prices are not per hour, but per GB-hour. So multiply your second monthly price by 5. Not cheaper for more data, but definitely cheaper per GB.

Oops. Duh, that makes more sense. Updated.

May I ask what is the planned use case for the RDB/AOF replication? Are you expecting to have access to the snapshots while the instance is running, or you just need them for import/export or durability reasons?

Disclaimer: I am an engineer at Google on the managed Redis team.

Use case for RDB backups: for rather large redis datasets (>50GB) with long living keys (90days and beyond) I found it useful to be able to parse an RDB snapshot using the python rdbtools and iterate over the whole dataset, e.g. in order to migrate data to a different format. I found this usually more stable and reliable than using SCAN and the likes.

For this use case it seems the export feature that allows you to take a snapshot of the database at any given time might fit the needs. We will definitely consider this feature for the general availability release.

Thanks for the reply!

I wasn't aware of an export feature. As long as the export comes in a reasonable machine readable format that should be equally fine and would remove the need for access to RDB files for my use case.

Amazon Elasticache by comparison:

1.5GB is $0.034 per hour = $24.82/mo.

6GB is $0.182 per hour = $132.82/mo.

They just run Redis on stock EC2 hardware hence the odd GB numbers.

But one advantage of AWS is that with Reserved Instance pricing you could get those numbers down by 2/3.

I don't think this is Redis, this is something that fully supports the Redis protocol.

I wouldn't be that much surprised if underneath use a custom implentation.

Said so, arguably, RDB and AOF are not a concern of the user but of the administrator so I wouldn't expect them...

The standard tier is supposed to persist data (and it did, during maintenance events - it was an alpha, so yeah - there was no data loss), but not sure what they use as the logs are not yet available.

It's not data persistence per se, it's just replication to another instance in a different zone. Persistence is not currently available but plans are in place.

Disclaimer: I am an engineer at Google on the managed Redis team.

UPD: replication -> persistence not available

You mean persistence is not yet available?

"Redis persistence" to AOF or RDB is not currently available (since we are not even in Beta yet), but standard tier instances persist your data in another zone in case something goes wrong with the master instance.

Yup, but your original post said replication isn't available yet. I think you meant persistence.

Thanks for pointing that out. Fixed.

For comparison, here are the prices for managed Redis instances in Azure (Central US) [0]:

Basic Tier (single instance, no SLA)

1GB - $40.15/month

2.5GB - $65.70/month

6GB - $131.40/month

Standard Tier (Primary/secondary replicated instance, SLA)

1GB - $100.74/Month

2.5GB - $164.25/month

6GB - $328.50/month

Premium Tier (Cluster, w/persistence, SLA)

6GB - $405.15/month

[0]: https://azure.microsoft.com/en-us/pricing/details/cache/

Reply on news.ycombinator.com