当前位置:首页 > 报告详情

Shopee 上的实时 Lakehouse.pdf

上传人: 可*** 编号:991722 2025-12-07 20页 866.68KB

1、Real-time Lakehouse ShopeeLuo LiShopee Data Infra0102Practice03OptimizationScenario04Future PlanThe Stream Scenario of Shopee01Building Data Warehouse Based on CDC DataClassic Lambda architecture,resource waste,difficult to ensure the data consistency between stream pipeline and batch pipelineRequir

2、es external asynchronous merge tasks for MOR table,high data latency,resource consumption.Consistency ChallengeHow to build a data warehouse based on the business database and provide a unified data layer for batch processing and stream processing is the first problem we are facing now.Incremental C

3、omputation ScenarioIn the stream pipeline,the downstream task only need the data that has changed by upstream task.The problems of traditional process as below:Maintain a big Flink state as a full-view,hard for the stability of Flink tasksReuse the Flink state is not easyDifficult to trace the data

4、processNeed a changelog kind thing to trace the state of records and dataNear-real-time Dashboard ScenarioTo support near-real-time computing,latency less than 10min,due to the lack of suitable data storage,we tend to adopt a stovepipe data processing model.No data reuse,redundant processingAll the

5、computing logic is piled up in a single task,which makes the task complex and difficult to maintain.Need to an extra storage like ClickhouseNeed a storage layer to keep update the data and support near-realtimeanalysisNeed a storage layer which can support:change log and delta&streamingly update eas

6、y to manage high performance(update&analysis)cost efficient work cooperatively with flink02Typical Practice Based on Flink and PaimonFlink+Paimon Data IngestionWe provide users with data integration services from the database to the data warehouse.We have replaced Hudi with Paimon as the default dat

word格式文档无特别注明外均可编辑修改,预览文件经过压缩,下载原文更清晰!
三个皮匠报告文库所有资源均是客户上传分享,仅供网友学习交流,未经上传用户书面授权,请勿作商用。
根据《Real-time Lakehouse @ Shopee》的内容,以下是全文关键点的概括: 1. **数据仓库构建挑战**:传统Lambda架构资源浪费,数据一致性难以保证,MOR表合并任务延迟高,资源消耗大。 2. **增量计算场景问题**:Flink状态管理困难,数据追踪困难,需要类似changelog的机制。 3. **近实时仪表盘场景问题**:缺乏合适的数据存储,导致数据重用和冗余处理,计算逻辑复杂。 4. **Flink + Paimon实践**:消除批入管道,实现10分钟内数据从业务数据库到数据仓库的可见性,计算资源减少40%,存储空间节省10%。 5. **任务诊断系统**:通过Paimon的变更日志功能,实现Flink作业瓶颈自动分析,资源消耗减少50%。 6. **Paimon优化**:自动分支减少数据冗余和计算资源浪费,延迟数据丢失问题得到解决。 7. **未来计划**:研究使用Append-Only表替代Hive表,以及Paimon支持二级索引以增强Ad-hoc查询能力。
"Flink+Paimon,实时诊断秘诀!" "Paimon优化,存储效率翻倍?" "未来计划,Hive表升级新篇章?"
客服
商务合作
小程序
服务号
折叠