Aerospike vs. Azure SQL Database

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 found it's a great alternative for making older legacy applications work with online databases instead of only on-premises databases. We've converted over a dozen applications this way, and it has allowed our clients to have a distributed workforce using their applications without incurring the expense of a complete application rewrite.

Incentivized

• Low latency
• Stable
• Highly configurable
• increasing features

Incentivized

• Maintenance is always an issue, so using a cloud solution saves a lot of trouble.
• On premise solutions always suffer from fragmented implementations here and there, where several "dba's" keep track of security and maintenance. With a cloud database it's much easier to keep a central overview.
• Security options in SQL database are next level... data masking, hiding sensitive data where always neglected on premise, whereas you'll get this automatically in the cloud.

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

• One needs to be aware that some T-SQL features are simply not available.
• The programmatic access to server, trace flags, hardware from within Azure SQL Database is taken away (for a good reason).
• No SQL Agent so your jobs need to be orchestrated differently.
• The maximum concurrent logins maybe an unexpected problem.
• Sudden disconnects.
• The developers and admin must study the capacity and tier usage limits https://docs.microsoft.com/en-us/azure/azure-subscription-service-limits otherwise some errors or even transaction aborts never seen before can occur.
• Only one Latin Collation choice.
• There is no way to debug T-SQL ( a big drawback in my point of view).

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

This is best solution as a DBA one could expect from a service provider and as a cloud service, it removes all your hassles.

Incentivized

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

The interfaces are intuitive once you are familiar with all the functions. The ability to use different tools to interact with the platform, such as directly via a browser or code editors such as VS Code or Visual Studio is a great option and allows for integrating withn the project and other testing and developing tools.

Incentivized

We used the community edition.

Incentivized

We give the support a high rating simply because every time we've had issues or questions, representatives were in contact with us quickly. Without fail, our issues/questions were handled in a timely matter. That kind of response is integral when client data integrity and availability is in question. There is also a wealth of documentation for resolving issues on your own.

Incentivized

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

Incentivized

We moved away from Oracle and NoSQL because we had been so reliant on them for the last 25 years, the pricing was too much and we were looking for a way to cut the cord. Snowflake is just too up in the air, feels like it is soon to be just another line item to add to your Azure subscription. Azure was just priced right, easy to migrate to and plenty of resources to hire to support/maintain it. Very easy to learn, too.

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

• Perfect for small and medium databases, being very cost effective.
• As a Platform as a Service, there is no concern about patches, upgrades and end of life.
• Be aware of security and network capabilities. The service cannot run in the VNET as Azure Virtual Machines do.