Apache Geode vs. NetApp SnapMirror

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

NetApp SnapMirror is a no-brainer when it comes to retaining an offsite backup for disaster recovery purposes. The backbone of the product is the Snapshot technology built into NetApp technology. In my experience, the Snapshot/SnapMirror software has been flawless and very dependable. The only piece that I can see adding in the future is potentially connecting SnapMirror to the cloud as an additional backup destination.

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

• Takes very quick copies of data.
• Ensures easy access.

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

• Integrate with other technology providers.
• Improve the initial Synch Process.
• Make custom schedule creation easier.

Incentivized

Very well versed and a good product to deal with downtime to recover from the failure is pretty good. Also, NetApp's engagement on Incident calls is very professional and humble. I would give a 100% rating to this product as I have been working on this for the past 5 years. It is stable, fast and highly reliable

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

Never contacted support

Incentivized

NetApp support has always been great. With the NetApp Auto-support system/web portal, the visibility into your NetApp storage is incredible. There have been times when I've been contacted by them for an issue that I haven't even discovered yet. For example, I received a call 20 minutes after a drive failed in our filer. I hadn't checked my email at that time and therefore didn't see the alert.

Incentivized

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

Incentivized

Over the years we have transitioned to NetApp SnapMirror for all our storage needs. However, due to the short life cycle of support, it is cost prohibitive to maintain after support is ended. The main reason we have liked NetApp SnapMirror due to the many options and standardized management capabilities and flexible options for provisioning and setup of storage.

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

• Enables us to recover data very quickly reducing time to recreate documents.

Incentivized