Ask HN: would you use a shared memcached hosted on popular VPS sites?
I wondered what are is your opinion on something that might be useful for VPS users. Take Linode as an example: the traffic between linode VPS is free inside the same datacenter.
Regarding memcache, when you need another memcached node, you would need to pay another VPS, only for the RAM. On Linode the ram cost is exactly 25.6 MB/$ no matter the plan you choose.
Imagine a service that would let you rent a shared memcached server for, say, 5 dollar to access a (max) 400MB memcached. Each memcached server would be limited to, say, 10 users. You would then have access to potentialy tens of MB from a fast memcached near your existing VPS at Linode.
This memcached would be shared: you would need to have unique keys, prefixed, for example, by a unique string. You could not store sensitive data on it, as anyone could read/destroy your cache, but depending on your application, that could not be a problem for you. I hear you, you are thinking : but that's not useable! What if everyong is deleting my cache the whole time ? Well, I answer you : there must be a way to avoid that ! SASL is one answer. That's not the question right now as I'm just thinking about the interest of people in such a thing.
Would you use such a service ? How much are you willing to pay to have access to such a memcached shared instance?
Thanks for taking the time to reply ! Contact me on #startups (nick henri) if you want to chat :)
ps: the goals would be to have many memcached servers in the different linode datacenters, as well as EC2, slicehost, etc..
14 comments
[ 3.6 ms ] story [ 39.9 ms ] threadWhat is the value of sharing a memcached instance? If all you're selling is memory, why not just run multiple memcacheds?
But what If i only need 100MB of memcached, and I don't want to pay 20$/month for that ?
Sure, one could sell memcached memory, with many instances per linode node. But my question is more about getting super-lower memcached for not critical data (if people put sessions in it, they misuse the service, they take their risks..). By sharing the bucket with people, can you afford to pay 5$/month for a part of a 400MB bucket ?
See http://www.slideshare.net/sensepost/cache-on-delivery on what can be done with a publicly accessible memcache daemon.
Instead of having to worry about adding a new memcache host I'd also love if you could handle it on your end. If all of a sudden I need a crapton of memory my mcahe would "expand". I'd get charged for that crapton.
Just some ideas brainstorming.
Basically, make it easy for me to optimize my cache store:).
If your app needs a memcached instance then those $20 bucks are likely a rounding error on the hosting bill either way.
And If you just want one for testing then a tiny <50M memcached on the local instance will carry you a long way.
Even ignoring the glaring security and technical concerns, I just don't see a use-case for this.