Apache Geode vs. CData Sync

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

Evidently, CData Sync is an excellent middleware tool that is perfect for syncing data between systems. It is especially suitable and works well on SQL servers, DB2, MySQL, and Snowflake, and some of their brothering domains. However, it is a limitation in working with Sage 50 API. But if it is extracted with ODBC, it works well.

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

• Effortless use of no-code interfaces on data pipelining on.
• High demand numbers of sources and destinations.
• Works with even snowflake, with no error occurrence.
• It uses ETL - (Extract / Transfer / Load).
• It enhances data extraction and database support.

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

• Although efficient for SQL servers and MySQL, as well as Snowflake. It is not strong for other database engines, and an upgrade on this would do a lot.
• The installation process is manual as opposed to the cloud installation it should be.
• A feature of syncing auto increment ID key, that will help in existing data management.

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

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

Incentivized

Tableau is another similar software tool, unlike CData Sync, rather transforms data into actionable insights. While CData Sync works with automation, Tableau uses a drag box on its AVA, which in turn slows the work speed on the syncing of data. Over the years, I enjoyed the friendly and customizable option of CData Sync over Tableau's.

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

• Reserves resources by covering human power via its automated sync method.
• Saves time: on launching data collectively into a compatible domain.

Incentivized