Apache Geode vs. Azure Cosmos DB

The biggest advantage of using Apache Geode is DB like consistency. So for applications whose data needs to be in-memory, accessible at low latencies and most importantly writes have to be consistent, should use Apache Geode. For our application quite some amount of data is static which we store in MySQL as it can be easily manipulated. But since this data is large R/w from DB becomes expensive. So we started using Redis. Redis does a brilliant job, but with complex data structures and no query like capability, we have to manage it via code. We are experimenting with Apache Geode and it looks promising as now we can query on complex data-structures and get the required data quickly and also updates consistent.

Incentivized

NoSQL platforms are very useful when it comes to security, speed, accuracy, high accessibility with high read and write power. Everything is managed under the cloud and we have the various capabilities of Azure and support for Microsoft products with us. Flexibility in price and variety of features, as well as real-time results, are some of the popular [features] of this platform.

Incentivized

• Super Fast data pull/push
• Provided ACID transactions, so it works like a SQL Database
• Provides replication & partitioning, so our data is never lost and extraction is super fast. NoSql like properties

Incentivized

• Turn-key geo-redundancy with multi-master writes is unprecedented and unparalleled in the industry!
• Guaranteed low latency makes Cosmos DB an excellent fit for most of our performance-intensive situations.
• The tunable consistency model simplifies so many challenges in distributed systems engineering that otherwise require advanced knowledge of computer science topics. I continue to be impressed at how Cosmos DB has abstracted away so much complexity.

Incentivized

• Needs more supporting languages. Out of box Python, Nodejs adapters would be wonderful
• Currently it supports just KV Store. But if we could cache documents or timeseries data would be great
• Needs more community support, documentation.

Incentivized

• When searching by default, it is case sensitive, which must be changed by default
• In many ways, the price should be more flexible according to the requested facilities, because the price is very expensive for startup companies.
• It is not fully compatible with most common Streaming Analytics tools applications and developers should be worked on it

Incentivized

It's efficient, easy to scale, and works. We do have to do a bit of administration, but less now than when we started with this a couple of years ago. Microsoft continues to improve its self-management capability.

Incentivized

Still Experimenting. Initial results are good. we need to figure out if we can completely replace Redis. Cost wise if it makes sense to keep both or replacement is feasible.

Incentivized

Like I said, Cosmos is the way to go. From all of the services that Azure has, Cosmos is very robust in terms of usability. It's ever-evolving and integrates with other applications seamlessly. The interface is pretty easy to understand. I implemented various solutions for my company and Cosmos was one of them.

Incentivized

Never contacted support

Incentivized

The support team is very responsive and we are generally satisfied with Microsoft support, in my opinion support team of a product and service is just as valuable as its quality and performance. Telephone answering, 24-hour hotline, email support and ticketing are excellent.

Incentivized

Still Experimenting. But looks promising as it has query capabilities over complex data structures

Incentivized

Azure Cosmos DB for MongoDB is more affordable than many other solutions and works incredibly well if you're within the Azure ecosystem.

Incentivized

• Still experimenting so difficult to quote
• For a small size project/teams might be an overkill as it still has certain learning curve
• For Medium to large projects with complex Data Structures that need to be queried with a fast o/p it definitely works

Incentivized

• Expensive but works if your infra is on Azure data center.
• No latency and nearly no downtime.
• Takes time for end users to adapt.

Incentivized