Tagged articles
log system
12 articles · Page 1 of 1
This article traces the evolution of Ctrip’s travel product log platform—from a single‑table DB approach to a platform‑wide ES + HBase solution—detailing the challenges of massive data volume, the architectural decisions, RowKey design, write and query flows, and the subsequent extensions that enabled billion‑scale log storage and fast retrieval.
CtripESHBase
0 likes · 17 min read

This article recounts the evolution of Ctrip's vacation product log platform—from a single‑table DB solution to a platformized ES + HBase architecture—detailing the challenges of massive data volume, the design of RowKey, write and query flows, and the subsequent business and supplier empowerment.
BackendElasticsearchHBase
0 likes · 14 min read

This article describes the development trajectory of Ctrip's travel product log system, detailing its three major phases—from a single‑table DB approach to a platform‑based solution and finally an empowered version—while discussing technical challenges, design decisions, and the implementation of HBase, Elasticsearch, and related components to handle billions of log entries efficiently.
BackendElasticsearchHBase
0 likes · 15 min read

This article details the evolution of Ctrip's vacation product log system—from a simple single‑table DB in 2019, through a platformized ES + HBase architecture with custom RowKey design, to a V3.0 version that adds business and supplier empowerment, scalable storage, advanced search, and flexible data presentation for billions of daily change records.
BackendESHBase
0 likes · 13 min read

This article details the three‑stage evolution of Ctrip's vacation product log system—from a simple single‑table DB approach, through a platform‑based ES + HBase solution, to a scalable V3.0 architecture that improves storage, search, and business empowerment while handling billions of log entries.
BackendElasticsearchdata pipeline
0 likes · 16 min read

This article details the evolution of ByteDance's TLS (Tinder Log Service) from a Loki‑based prototype to an EB‑scale, cloud‑native log system, covering its core properties, data organization, architecture, caching, hybrid storage, private codec, ecosystem compatibility, intelligent features, and real‑world case studies.
ByteDanceData StorageTLS
0 likes · 24 min read

A production logging system became unavailable due to Kafka backlog alerts, prompting an investigation that uncovered read‑only ClickHouse tables caused by mismatched Zookeeper metadata after a TTL policy change, leading to a step‑by‑step recovery involving Zookeeper restarts, metadata fixes, and table reconstruction.
ClickHouseCluster RecoveryFlink
0 likes · 9 min read

This article details the evolution of Ctrip's log infrastructure, describing the shift from fragmented departmental logging to a unified Elasticsearch-based platform, the migration to ClickHouse for cost‑effective, high‑performance storage, and the subsequent Log 3.0 redesign that leverages Kubernetes, sharding, and a unified query governance layer to handle petabyte‑scale data.
ClickHouseETLElasticsearch
0 likes · 16 min read

Taobao redesigned its mobile client’s diagnostics and logging architecture—introducing scenario‑based monitoring, standardized log protocols, snapshot collection, and change‑tracking SDKs—to meet a 5‑minute response, 15‑minute identification, and 60‑minute recovery goal, dramatically improving issue detection, analysis, and resolution efficiency.
Operationsclient-sidelog system
0 likes · 17 min read

This article describes the requirements, architecture, API design, database selection, retention policies, security measures, and performance optimizations of a new iOS log system that records business, network, and player logs, uses WCDB for storage, and employs active pull and encrypted chunked uploads to improve issue diagnosis.
LoggingSecurityWCDB
0 likes · 16 min read

This article describes the design and implementation of a seller log system, detailing the use of Kafka for high‑throughput messaging, Storm for real‑time stream processing, Elasticsearch for hot‑data search, and HBase for cold‑data storage, along with challenges faced and optimization solutions.
KafkaStormlog system
0 likes · 12 min read

The article chronicles the development of Tongcheng's centralized log system from early file‑based logging through a MongoDB‑based solution to the current multi‑layer architecture using Flume, Elasticsearch, and Hadoop, highlighting design decisions, challenges, and future improvement plans.
Flumebig datalog system
0 likes · 7 min read
