Live data from Hacker News

Show HN: Key/Value Store as-a-Service

keyvalue.xyz

21–30 of 34 posts

Re: Show HN: Key/Value Store as-a-Service

#23

Since each new key request creates a uuid, wouldn't someone need to store that uuid in local key/value store in order to retrieve values from this k/v? $ curl -X POST http://api.keyvalue.xyz/new/key1 http://api.keyvalue.xyz/3b629f4d/key1 $ curl -X POST http://api.keyvalue.xyz/new/key2 http://api.keyvalue.xyz/3eea0e2c/key2

I guess their primary target isn't generating keys on the fly, but rather using already defined keys (set / get value). But I agree, it would make sense to have the ability for reusing an existing UUID.

Re: Show HN: Key/Value Store as-a-Service

#24
post #8

>Do you need high available, flexible and dynamic key/value store for coordination, notification, feature flagging and more? Doesn't exactly evoke confidence. Are they being explicit that the free tier won't have availability. Is there an SLA or even an estimate?

Thank you for pointing this out! I have already updated the text for enterprise setup because that was not the intention.

SLA is in progress but the system is planned to be up & free with the current usage.

Re: Show HN: Key/Value Store as-a-Service

#29
A web front end to memcache? I wrote one in Python 5 years ago. This is trivial stuff, although configuring your nginx proxy or whatever, takes some study. SSL can have 0 security if you do it wrong. I like the HIPAA advice from here https://luxsci.com/blog/level-ssl-tls-required-hipaa.html
Post reply on HN