How this guide is sourced
Every version number, release date, price and benchmark figure on this site comes from a source we can name, and the page names it. Where no primary source publishes a figure, the page says so instead of estimating one.
Where each kind of figure comes from
| Figure | Primary source | Example page |
|---|---|---|
| Engine versions and release dates | Project release pages: github.com/redis/redis, github.com/valkey-io/valkey, memcached.org and its release notes | /latest-stable-versions/ |
| License history | Redis Inc announcements and license texts, the Linux Foundation's Valkey announcement (28 March 2024), OSI license list | /redis-license-timeline/ |
| Managed-service engines and versions | Provider documentation: AWS ElastiCache engine-versions guide, Google Cloud Memorystore supported-versions and deprecation pages, Microsoft Learn | /managed-options/ |
| Managed-service prices | The provider's own pricing page or price-list API, with the region stated (for example us-east-1 on AWS, Iowa us-central1 on Google Cloud) | /managed-options/gcp-memorystore/ |
| Benchmarks | The publisher's own write-up, labelled vendor (published by a company selling the engine or a service on it) or independent, with hardware and workload stated | /benchmarks/ |
Prices
Cloud prices are read from the provider's pricing page on the date shown, in one stated region, on demand unless a commitment discount is named. They change by region and over time, so treat them as a starting point and confirm your own region before you budget. Worked examples show their arithmetic, so you can redo them with your own node count.
Benchmarks
Throughput and memory figures are reported as the publisher measured them, with the hardware, workload and engine versions they used. A benchmark published by a company that sells one of the engines, or a service built on it, is labelled as a vendor benchmark. We do not average or blend figures from different tests, and we do not run our own load tests.
What the dates mean
The Updated date on a page is when its content last changed, taken from the site's version history at build time; nobody types it by hand. A Checked date next to a table or a list of sources is the day those figures were re-read at their source. The two can differ: a page can be reworded without its prices being re-read, and prices can be re-checked without any wording changing.
Keeping pages current
Pages are re-checked on a rotating schedule and when a source changes (a new engine release, a pricing change, a deprecation notice such as Google's retirement of Memorystore for Memcached). Errors reported by readers to questions@redisvsmemcached.com are checked against the source and fixed on the page. Who publishes the site is on the about page.