Until then, this makes sense only for mid-large scale memcache deployments, similar to Amazon's RDS.
Until then, this makes sense only for mid-large scale memcache deployments, similar to Amazon's RDS.
It would be a real killer if they had incremental pricing (per-GB-hour) with an adjustable high watermark / replica count, and a name/port-based endpoint that always worked and routed requests to the proper cache server.
Edit: Note that a lot of that profit gets eaten up in underutilized capacity, this is just a simplistic analysis.
However, the automatic failovers is very nice. From Vogel's blog: "Amazon ElastiCache automatically detects and replaces failed Cache Nodes to protect the cluster from those failure scenarios." That is definitely nice.
Elasticache does seem to be sitting in an awkward middle ground between renting of instances and paying for usage in an API.
Edit: after thinking about it more and reading some of the comments, I think an ideal setup would be an API to a memcached like datastore with buckets so I can specify max-size, redundancy, expiration methods, etc on a per bucket basis. Even nicer setup would be all of that plus redundancy and HA across availability zones and regions.
Raising the question of why Amazon didn't adapt its S3 API to the task, and then layer an optional memcached-compatible wrapper on top of it.