Re:Show HN: My first tiny web service, a simple key/value store
by donutdan4114 on Sunday May 24, 2015 @04:54PM
(#9597550)
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.
Re:Show HN: My first tiny web service, a simple key/value store
by paulasmuth on Sunday May 24, 2015 @05:00PM
(#9597566)
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)
Re:Show HN: My first tiny web service, a simple key/value store
by donutdan4114 on Sunday May 24, 2015 @05:06PM
(#9597597)
Thanks for the feedback, I updated the pricing message to be clearly max-keys of 100,000 for gold plan. All feedback appreciated.
Re:Show HN: My first tiny web service, a simple key/value store
by Chris911 on Sunday May 24, 2015 @05:55PM
(#9597781)
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.
Re:Show HN: My first tiny web service, a simple key/value store
by donutdan4114 on Sunday May 24, 2015 @06:13PM
(#9597832)
Max value is 64kb
Re:Show HN: My first tiny web service, a simple key/value store
by donutdan4114 on Sunday May 24, 2015 @05:01PM
(#9597574)
Okay I will update the messaging to be more accurate. Good feedback.
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.