If they don't know this much, what else don't they know? Not to mention they don't disclose anything about the team or company other than it is "Made with Love in Istanbul". No reason not to assume its a kid who has never hosted a production service in their life.
It feels like this is a missed opportunity to use a content-addressable store. It would be super valuable to have the capability of hashing content and knowing when you don't need to re-download it.
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?
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.
Is there a way to batch requests? I'd like to be able to get/set more than one value at a time. It'd also be nice to be able to get a list of all my keys just in case I forget.
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
I think this shouldn't be used to store application or user data, but could be actually useful for less important data used by cron scripts and scheduled jobs for which you would otherwise use a small local database or text files.
33 comments
[ 15.2 ms ] story [ 95.4 ms ] thread> http://api.keyvalue/xyz/c98ab8e0/myKey
`api.keyvalue/xyz` vs. `api.keyvalue.xyz`
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?
SLA is in progress but the system is planned to be up & free with the current usage.
A wide range of popular key/value stores exist and are easy enough to manage. Cloud provider also offer cheap managed stores.
$ 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
- how long will my data be stored for?
- how big can a single key be?
- how many requests can I make per hour/day?
https://jsonbin.org/