Doesn't latency kill the usefulness of any cloud based cache?
Most of the AWS services are designed to be used together, so you'd have an EC2 instance in the same data center as the memcache service.
Announcing Amazon ElastiCache - Managed Memcached
21–30 of 37 posts
Re: Announcing Amazon ElastiCache - Managed Memcached
#22So this is just a simple way to get some memcached instances running. I guess it makes sense for amazon to target memcached since it's still the most popular caching system in use, and probably the easiest for newbies to get into, but it is very old technology at this point. There is no built in support for clustering, replication, or durability. There are solutions out there that provide a much better feature set. H…
It may or may not be memcached -- it merely speaks the same protocol. I would not be totally amazed if something else is running underneath now or in future.
Re: Announcing Amazon ElastiCache - Managed Memcached
#23This would have been more awesome if the clusters had an address and handled the sharding for you.
As it stands, getting a memcached server up and running is so trivial that this probably isn't worth the extra cost for anyone on a small scale and already using things like chef or puppet.
Re: Announcing Amazon ElastiCache - Managed Memcached
#24So this is just a simple way to get some memcached instances running. I guess it makes sense for amazon to target memcached since it's still the most popular caching system in use, and probably the easiest for newbies to get into, but it is very old technology at this point. There is no built in support for clustering, replication, or durability. There are solutions out there that provide a much better feature set. H…
It may or may not be memcached -- it merely speaks the same protocol. I would not be totally amazed if something else is running underneath now or in future.
That is definitely plausible, but I'm more referring to the feature set, i guess i would clarify as the contract between them and the developer. That is basically memcached, from what i understood from their blog posts. As far as memcached itself goes, i hear it does what it does quite well, but that's ot.
Re: Announcing Amazon ElastiCache - Managed Memcached
#25Amazon Y U NO Redis?
Re: Announcing Amazon ElastiCache - Managed Memcached
#26This would be nice if the cheapest option didn't end up costing 3 times as much as my entire AWS server itself.
Re: Announcing Amazon ElastiCache - Managed Memcached
#27Earlier quoted context omitted.
Agreed, the value add isn't very high, especially since the pricing is higher than EC2. Surely there are some economies that could be found on servers with no disks and reduced CPU requirements? I wonder if ECC could even be done away with if they checksummed all the stored values? It would be a real killer if they had incremental pricing (per-GB-hour) with an adjustable high watermark / replica count, and a name/por…
I agree, that would be great. Let's start a company that does that.
The problem is that you need to provide the other services as well. Having your database and application server in one datacenter, but your memcached instance in another would reduce the use-cases because of latency and bandwidth restrictions.
Re: Announcing Amazon ElastiCache - Managed Memcached
#28Is the failover mechanism just a hardware replacement where you need to repopulate the cache or are they doing some kind of "slave" hotswap that the replaced hardware already has the cache?
Re: Announcing Amazon ElastiCache - Managed Memcached
#29I don't understand. Wouldn't network IO latency be higher than memory access? and wouldn't that beat the purpose of having a memcache?
Re: Announcing Amazon ElastiCache - Managed Memcached
#30So this is just a simple way to get some memcached instances running. I guess it makes sense for amazon to target memcached since it's still the most popular caching system in use, and probably the easiest for newbies to get into, but it is very old technology at this point. There is no built in support for clustering, replication, or durability. There are solutions out there that provide a much better feature set. H…
It may or may not be memcached -- it merely speaks the same protocol. I would not be totally amazed if something else is running underneath now or in future.
In the FAQ it states "Each Cache Node runs an instance of the Memcached software and has its own DNS name and port". So it looks like it is running memcached and not just talking it.