Mage vs. SAP Replication Server

Mage is well-suited for probability score for uptake of every product is calculated for customers using ML/ Regression models, choosing customers for a product/ Top products for a customer, based on the requirement and Identifying popular product combinations using association rules from Market Basket Analysis (or affinity Analysis)\Bundle these products as combos.

Incentivized

I asked questions about a warm standby and multicast replication. We ended up using bi-directional replication and a warm standby db. Having 3 or more live OLTP DB's where each was read-write was going to be difficult to manage for contention if the same table was being updated. We stuck with an easier solution to have only two OLTP's, and then used additional DB's as read-only DW's.

Incentivized

• Ranking algorithms.
• Cloud-based tool.
• Increase user engagement.

Incentivized

• guaranteed delivery
• high availability
• scalable
• low latency
• data transformation

Incentivized

• Acquisition Contribution.
• Business Intelligence Reporting.
• Data Destinations.

Incentivized

• Data Reconciliation Functionality.

Incentivized

SAP support has been outstanding. They have quick response times and always meet their SLAs. Any time we have an issue that needs to be researched they are able to get back to us quickly with resolution.

Incentivized

Mage was the easiest in terms of ease of implementation due to its no-code functionality. However, Mage doesn't have a whole ecosystem like AWS and slightly falls behind there.

Incentivized

Hands down Sybase has the best replication

Incentivized

• Business Understanding.
• Data Acquisition and Understanding.
• Data Modeling and Evaluation.

Incentivized

• A positive is that it allow quick business decision making on the basis of real time data. Huge time saving for business.

Incentivized