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.<p>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.
It's an interesting idea, but I'm not sure there are very many potential use cases. Mostly, I can see using this client-side so that I don't need to set up a back end myself, but if I understand correctly, that's not really possible since you have to keep the API key private.
I've used parse.com free account, created a class named 'cache' with columns 'key' & 'value'. The free plan's capacity is like 100k bigger than your highest paid plan. Sorry, I do not see the advantage of your service.
>> curl <a href="https://tinycache.io/api/v1/YOUR_API_KEY/mysecretkey?decrypt=supersecretkey" rel="nofollow">https://tinycache.io/api/v1/YOUR_API_KEY/mysecretkey?decrypt...</a><p>Passing the key as a GET parameter is not super-secret, I would avoid doing that if possible.
I like the idea of the pixel font, but find one that doesn't make the N look ugly. Silkscreen's usually a safe choice.<p>And I'd make the dev account more than 100 hits/day. I could easily go through that while actually coding, fixing bugs, repeat.<p>Since the use case is about quick, lightweight projects, I'd make creating an account optional until you need it. I'd want this to be as frictionless as possible, so that if I'm in the throes of coding and want the simplest possible key value store, I can just type in a URL like <a href="https://tinycache.io/api/myemail@address.com/CACHE_KEY" rel="nofollow">https://tinycache.io/api/myemail@address.com/CACHE_KEY</a> and know it'll work without having to break out of my editor.
I'd really caution against your pricing structure. Unlimited access to a million keys is no joke, I've run some rather large memcached servers and none of them were $20/month.<p>You should pricing should always reflect the true cost + your desired profit margin. I'd probably be charging hardware usage + 15% before even factoring in the value of the service itself.<p>Right now I'd say you're vastly too cheap; don't think about the costs solely as your servers but what's the value you've added to memcached/caching? Surely that's more than what you're charging?<p>Tldr; Keep the small plans cheap but make the big plans waaay more expensive. Those using the biggest plans are finding the most value.
Hey everyone, all feedback is appreciated. The main point of the service is speed, and ease-of-implementation. It's very easy to setup an account, and the API is very simple.<p>Always curious what fellow HNer's opinions are.
Awesome I (a human) love it. Trying to sign up but I'm having this problem:
<a href="https://www.dropbox.com/s/yd91j84bmrg4w0w/Screenshot%202015-05-24%2014.49.33.jpg?dl=0" rel="nofollow">https://www.dropbox.com/s/yd91j84bmrg4w0w/Screenshot%202015-...</a>
For personal use, this page explains how to setup a local script to work with the API. Makes it super easy to access whatever data you want across different computers.<p><a href="https://tinycache.io/documentation/examples" rel="nofollow">https://tinycache.io/documentation/examples</a>