Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Navina Ramesh

dblp:204/3829 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 2017
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Databases, data management, data science and information retrieval · 1

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Databases, data mining, and information retrieval
1 paper
Data stream processing · 100%
Computer architecture, parallel and distributed computing, and storage systems
1 paper
Distributed systems · 100%

Topics — the 4 heaviest of 4, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Data stream processing
fault tolerance
0.312017
Stateful Scalable Stream Processing at LinkedIn · Proc. VLDB Endow. 2017
Data stream processing › stream processing systems
stateful stream processing
0.312017
Stateful Scalable Stream Processing at LinkedIn · Proc. VLDB Endow. 2017
Distributed systems › fault tolerance
failure recovery
0.312017
Stateful Scalable Stream Processing at LinkedIn · Proc. VLDB Endow. 2017
Distributed systems
fault tolerance
0.312017
Stateful Scalable Stream Processing at LinkedIn · Proc. VLDB Endow. 2017

Methods — techniques the papers use, named apart from their topics

host affinity scheduling · 0.6changelog · 0.6
YearPublicationVenuePosition
2017 Stateful Scalable Stream Processing at LinkedIn
abstract
Distributed stream processing systems need to support stateful processing, recover quickly from failures to resume such processing, and reprocess an entire data stream quickly. We present Apache Samza, a distributed system for stateful and fault-tolerant stream processing. Samza utilizes a partitioned local state along with a low-overhead background changelog mechanism, allowing it to scale to massive state sizes (hundreds of TB) per application. Recovery from failures is sped up by re-scheduling based on Host Affinity. In addition to processing infinite streams of events, Samza supports processing a finite dataset as a stream, from either a streaming source (e.g., Kafka), a database snapshot (e.g., Databus), or a file system (e.g. HDFS), without having to change the application code (unlike the popular Lambda-based architectures which necessitate maintenance of separate code bases for batch and stream path processing). Samza is currently in use at LinkedIn by hundreds of production applications with more than 10, 000 containers. Samza is an open-source Apache project adopted by many top-tier companies (e.g., LinkedIn, Uber, Netflix, TripAdvisor, etc.). Our experiments show that Samza: a) handles state efficiently, improving latency and throughput by more than 100X compared to using a remote storage; b) provides recovery time independent of state size; c) scales performance linearly with number of containers; and d) supports reprocessing of the data stream quickly and with minimal interference on real-time traffic.
Shadi A. Noghabi, Kartik Paramasivam, Navina Ramesh, Jon Bringhurst, Indranil Gupta, Roy H. Campbell
Proc. VLDB Endow.4