Aerospike vs. IBM IMS

We were developing an advertisement time auction application, where we had to store the client's personal details, advertisement-related details, location, and many other details. Moreover, we required a promotion, cookies, and a few more details from the front end. All this information is heavy in terms of size and cannot be lost if the server crash. So, we required an extremely fast disk database with high scalability and low throughput.

Incentivized

We have built a database of a network of bank branches with all the needs of security and recovery/restart. It requires knowledge of obsolete maintenance languages and perhaps it is too rigid in the schemes.

Incentivized

• Low latency
• Stable
• Highly configurable
• increasing features

Incentivized

• Security
• Reliability
• Big volume of data and good performance

Incentivized

• Load balancing per network segments.
• Reduction in price.
• Cross datacenter replication usage isn't so straightforward. Sometimes cross dc replication can have issues of bad data..

Incentivized

• Certainly, not being a DB relational penalizes its use
• It should be more flexible
• Open up to more recent languages

Incentivized

If money isn't an issue, and you're not on the cloud, then I'd go with Aerospike. If you're the cloud ie, aws or azure, then i'd stick with dynamoDB or Cosmos then. Aerospike is definitely not something you want to put into the cloud. It doesn't work well w/ cross regions. If cross DC, you'll have to write some stuff for data integrity checks.

Incentivized

Could be easier to use and install. Also developer experience needs some work

We used the community edition.

Incentivized

Aerospike is much more performant than MongoDB, however there is much greater community adoption and support for mongo

Incentivized

Essentially, for a question of reliability and scalability, the performance has always been of an enterprise level. The utilities are efficient and effective.

Incentivized

• Being able to power the same workload on a fraction of the servers has led to better ROI for my application.
• Less servers needed also meant less time to manage the cluster, leading to savings in engineering time

• The investment made about 20 years ago that has been fully repaid
• Reliability and security of investments
• Unfortunately, it is quite outdated and therefore maintenance costs are higher because the skills are not always available.

Incentivized