问题描述
Aerospike 是一个键值、内存、可操作的 NoSQL 数据库，具有 ACID 属性支持复杂的对象并且易于扩展.但是我已经使用了一些完全相同的东西.
Aerospike is a key-value, in-memory, operational NoSQL database with ACID properties which support complex objects and easy to scale. But I have already used something which does absolutely the same.
Redis 也是一个键值对、内存中(但持久化到磁盘)NoSQL 数据库.它还支持不同的复杂对象.但与 Aerospike 相比，Redis 使用了很长时间，已经有一个活跃的社区，并在其中开发了很多项目.
Redis is also a key-value, in-memory (but persistent to disk) NoSQL database. It also support different complex objects. But in comparison to Aerospike, Redis was in use for a lot of time, already have an active community and a lot of projects developed in it.
那么aerospike和redis等其他no-sql键值数据库有什么区别.有没有什么地方更适合空刺.
So what is the difference between aerospike and other no-sql key-value databases like redis. Is there a particular place which is better suited for aerospike.
附言我正在寻找在现实世界中至少使用过这些数据库中的一个(最好是两个)并且没有实际生活经验(不是从官方网站复制粘贴)的人的答案.
P.S. I am looking for an answer from people who used at least one of these dbs (preferably both) in real world and havend real life experience (not copy-pastes from official website).
推荐答案
如果非要用一个词来回答，那就是它的性能".Aerospike 的性能比现有的任何集群 nosql 解决方案都要好得多.每个节点的更高性能意味着更小的集群，从而降低 TCO(总拥有成本)和维护.Aerospike 执行自动集群、自动分片、自动重新平衡(当集群状态更改时)，其中大部分需要在其他数据库中手动执行.
If it has to be answered in one word, its "performance". Aerospike's performance is much better than any clustered-nosql solutions out there. Higher performance per-node means smaller cluster which is lower TCO (Total Cost of Ownership) and maintenance. Aerospike does auto-clustering, auto-sharding, auto-rebalancing (when cluster state changes) most of which needs manual steps in other databases.
我说集群"是因为我不想在该组中混合 redis(尽管 redis 集群处于测试阶段).Aerospike 和 redis 的纯内存性能将具有可比性.但是 Redis 期望在应用层处理很多事情，例如分片、请求重定向等.尽管 redis 有一种持久化的方法(快照或 AOF)，但它有自己的问题，因为它更像是一个插件.Aerospike 是本机开发的，考虑到了持久性.redis的集群还涉及到设置master slave等.你可能想看看这个talk 比较和对比 redis 与 aerospike.
I said "clustered" because I dont want to mix redis in that group (though redis clustering is in beta). Pure in-memory performance of Aerospike and redis will be comparable. But Redis expects a lot of things to be handled at the application layer like sharding, request redirection etc. Even though redis has a way to persist (snapshot or AOF), it has its own problems as its designed more like an addon. Aerospike is developed natively with persistence in mind. The clustering of redis also involves setting up master slave etc. You may want to take a look at this talk comparing and contrasting redis vs aerospike.
这篇关于aerospike 与其他键值 nosql 数据库有何不同?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！