SAP HANA vs. MemSQL
Slow Data Ingest
Slower transactions and poor data ingest throughput due to architecture. Unable to deliver parallel lock-free ingest for streaming data.
Scale-out shared-nothing architecture provides a robust parallel execution engine for queries. Proven with industry benchmarks: TPC-C, TPC-H, & TPC-DS.
Not natively distributed; requires manual sharding and costly data re-distribution.
Scale-out architecture efficiently and quickly responds to growing workloads, leveraging commodity hardware without add-ons or specialized tuning expertise.
Hardware and software configurations tightly integrated, resulting in challenging patches and upgrades that tie up DBA resources.
Single Product Simplicity
Rapidly deploy the integrated software-only environment on standard hardware for dramatically reduced complexity and improved manageability.
Requires specialized hardware, maintenance contracts, database options, & upgrade fees. In-memory-only means higher TCO for OLAP workloads.
Simple, single-product subscription, with a software-only platform that’s easy to manage and patch, delivers performance with dramatic cost savings.
Requires specialized and certified hardware. Not DevOps-ready, resulting in complex admin operations. Downtime during scale out. In-built DR solution is inadequate.
DevOps-ready and deploy anywhere, including on-premises or any cloud. Leverages the MySQL wire protocol and JDBC/ODBC interface to integrate with the most popular data services and software tools.