Need advice about which tool to choose?Ask the StackShare community!
FoundationDB vs Memcached: What are the differences?
What is FoundationDB? Multi-model database with particularly strong fault tolerance, performance, and operational ease. FoundationDB is a NoSQL database with a shared nothing architecture. Designed around a "core" ordered key-value database, additional features and data models are supplied in layers. The key-value database, as well as all layers, supports full, cross-key and cross-server ACID transactions.
What is Memcached? High-performance, distributed memory object caching system. Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering.
FoundationDB and Memcached belong to "Databases" category of the tech stack.
"ACID transactions" is the primary reason why developers consider FoundationDB over the competitors, whereas "Fast object cache" was stated as the key factor in picking Memcached.
Memcached is an open source tool with 8.99K GitHub stars and 2.6K GitHub forks. Here's a link to Memcached's open source repository on GitHub.
So, we started using foundationDB for an OLAP system although the inbuilt tools for some core things like aggregation and filtering were negligible, with the high through put of the DB, we were able to handle it on the application. The system has been running pretty well for the past 6 months, although the data load isn’t very high yet, the performance is fairly promising
Pros of FoundationDB
- ACID transactions6
- Linear scalability5
- Multi-model database3
- Key-Value Store3
- Great Foundation3
- SQL Layer1
Pros of Memcached
- Fast object cache139
- High-performance129
- Stable91
- Mature65
- Distributed caching system33
- Improved response time and throughput11
- Great for caching HTML3
- Putta2
Sign up to add or upvote prosMake informed product decisions
Cons of FoundationDB
Cons of Memcached
- Only caches simple types2