HackerPapers

arXiv:2006.00064cs.DC

A Cloud Native Platform for Stateful Streaming

Scott Schneider, Xavier Guerin, Shaohan Hu, Kun-Lung Wu

Early discovery. Linked by one identifiable commenter. This paper is outside the main ranking; a mention is not an endorsement.

Abstract

We present the architecture of a cloud native version of IBM Streams, with Kubernetes as our target platform. Streams is a general purpose streaming system with its own platform for managing applications and the compute clusters that execute those applications. Cloud native Streams replaces that platform with Kubernetes. By using Kubernetes as its platform, Streams is able to offload job management, life cycle tracking, address translation, fault tolerance and scheduling. This offloading is possible because we define custom resources that natively integrate into Kubernetes, allowing Streams to use Kubernetes' eventing system as its own. We use four design patterns to implement our system: controllers, conductors, coordinators and causal chains. Composing controllers, conductors and coordinators allows us to build deterministic state machines out of an asynchronous distributed system. The resulting implementation eliminates 75% of the original platform code. Our experimental results show that the performance of Kubernetes is an adequate replacement in most cases, but it has problems with oversubscription, networking latency, garbage collection and pod recovery.

arXiv comments
18 pages, 11 figures, submitted to OSDI 2020
Journal reference
DOI
Subjects
cs.DCDistributed, Parallel, and Cluster Computing

On Hacker News

Linked by 1 identifiable commenter in 2 comments across 2 threads, from Nov 2020 to Aug 2021.

Comments linking this paper, per year.

Discussed in comments2 threads

    • This is the approach I take when I write, so this is how I try to write. I hope it is reflected in my first-author papers. Three papers from the past several years: https://www.scott-a-s.com/files/middleware2016_loadbalancing...…

      scott_sView on HNParent context

    • Me and my colleagues came up with an abstraction called conductors for the orchestration problem. Short version is that when you have some dependence on multiple resources being in a particular state before creating or updating yet another resource, use a conductor. They observe…

      scott_sView on HNParent context

Submitted to Hacker News

Connected through shared HN threads, not inferred similarity or a recommendation.