Hacker News Reader

Comment by paulasmuth | Hacker News Reader

I am not sure I understand the pricing and/or the service. What are your guarantees about dropping or not dropping keys? Obviously you can't sell unlimited memcache space for 20$/mo and you must protect against customers exhausting all your available resources.

So since it's quite obvious that there must be some limit and/or expiration policy I think you should really just spell it out on the page.

View on HN

We never drop keys unless the expire time is set. As long as someone isn't abusing the service by flooding it with random data, it will scale for them.

How do you determine if I am flooding your service with random data?

My understanding is that one of your main ideas is to encrypt the data so I am honestly wondering where you would even start to check if a user was randomly flooding you or legitimately storing lots of keys.

Not trying to pick nits here... My original point was that -- in my opinion -- it comes across slightly dishonest if you insist that there is no limit even when it's obvious there must be one. (I mean seriously, how many machines is this running on right now? Even if it's running on amazon/google you can only scale my backend up so much with 20$/mo)

Thanks for the feedback, I updated the pricing message to be clearly max-keys of 100,000 for gold plan. All feedback appreciated.

Another kind of abuse could be to store huge chunk of data per key. Even with 10,000 keys if each key stores a 50 MB JSON blob you're storage cost could go up quickly.

Max value is 64kb

Okay I will update the messaging to be more accurate. Good feedback.

Reply on news.ycombinator.com