Comparing Apache Hudi's™ MOR and COW Tables: Use Cases from Uber and Shopee
Blog post from Onehouse
Apache Hudi, developed by Uber in 2015, introduced the Merge-On-Read (MOR) table format as a solution to improve the inefficiencies of Copy-On-Write (COW) tables in handling big data analytics, particularly in scenarios involving frequent updates. While COW tables rewrite the entire file for any modification, resulting in inefficiencies for streaming data, MOR separates updates into changelog files, which are later merged, reducing write amplification. Uber utilizes COW tables for append-only data, such as user interactions in their app, ensuring fast query performance. On the other hand, Shopee, an eCommerce platform, employs MOR tables to handle update-heavy workloads like real-time user interactions, benefiting from efficient writes and reduced costs. These two table types, each serving distinct needs, offer companies flexibility in optimizing their data storage strategies depending on their specific requirements, with COW excelling in scenarios necessitating rapid reads and MOR providing advantages in environments with frequent data updates.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.