Conference on Innovative Data Systems Research · 2015 · 44 citations · 32 references
ComputingComputer ScienceComputer SystemsData ManagementDistributed SystemsParallel ComputingBatch ProcessingData IntegrationStream ProcessingBottleneck DetectionData-intensive ComputingDistributed File System ArchitectureIncremental ProcessingLarge-scale Data ProcessingParallel ProcessingPublish-subscribe SystemsStateful Stream Processing
The growing sophistication of data‑parallel processing systems has shifted the bottleneck from back‑end data stores to the data‑integration stack, which must now handle diverse back‑end systems with varying access latencies and integration requirements that legacy file‑system‑based stacks cannot meet. This paper introduces Liquid, a data‑integration stack designed to deliver low‑latency access for both near‑real‑time and batch workloads. Liquid achieves this through a two‑layer architecture comprising a stateful stream‑processing layer and a highly available publish/subscribe messaging layer, enabling incremental processing while remaining cost‑efficient and highly available. Our deployment of Liquid at LinkedIn, serving a data‑intensive platform with over 300 million users, demonstrates its practical viability in a large‑scale production environment.
With more sophisticated data-parallel processing systems, the new bottleneck in data-intensive companies shifts from the back-end data systems to the data integration stack, which is responsible for the pre-processing of data for back-end applications. The use of back-end data systems with different access latencies and data integration requirements poses new challenges that current data integration stacks based on distributed file systems—proposed a decade ago for batch-oriented processing—cannot address. In this paper, we describe Liquid, a data integration stack that provides low latency data access to support near real-time in addition to batch applications. It supports incremental processing, and is cost-efficient and highly available. Liquid has two layers: a processing layer based on a stateful stream processing model, and a messaging layer with a highly-available publish/subscribe system. We report our experience of a Liquid deployment with backend data systems at LinkedIn, a data-intensive company with over 300 million users.
32
Sanjay Ghemawat · Communications of the ACM · 2008 · 18.5K citations · Full text
The Hadoop Distributed File System
Konstantin V. Shvachko, Hairong Kuang, Sanjay Radia et al. · 2010 · 4.8K citations
Vinod Kumar Vavilapalli, Arun C. Murthy, Chris Douglas et al. · 2013 · 1.8K citations