Frantisek Hartman

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

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

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

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 · 77% Cloud and datacenter computing · 23%

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

TopicWeightPapersLastEvidence papers
Data stream processing
distributed stream processing
0.512021
Hazelcast Jet: Low-latency Stream Processing at the 99.99th Percentile · Proc. VLDB Endow. 2021
Data stream processing › stream processing systems
low-latency stream processing
0.512021
Hazelcast Jet: Low-latency Stream Processing at the 99.99th Percentile · Proc. VLDB Endow. 2021
Distributed systems › fault tolerance
exactly-once processing
0.512021
Hazelcast Jet: Low-latency Stream Processing at the 99.99th Percentile · Proc. VLDB Endow. 2021
YearPublicationVenuePosition
2021 Hazelcast Jet: Low-latency Stream Processing at the 99.99th Percentile
abstract
Jet is an open source, high performance, distributed stream processor built at Hazelcast during the last five years. Jet was engineered with millisecond latency on the 99.99th percentile as its primary design goal. Originally Jet's purpose was to be an execution engine that performs complex business logic on top of streams generated by Hazelcast's In-memory Data Grid (IMDG): a set of in-memory, partitioned and replicated data structures. With time, Jet evolved into a full-fledged, scale-out stream processor that can handle out-of-order streams and provide exactly-once processing guarantees. Jet's end-to-end latency lies in the order of milliseconds, and its throughput in the order of millions of events per CPU-core. This paper presents the main design decisions we made in order to maximize the performance per CPU-core, alongside lessons learned, and an empirical performance evaluation.
Can Gencer, Marko Topolnik, Viliam Durina, Emin Demirci, Ensar B. Kahveci, Ali Gürbüz, József Bartók, Grzegorz Gierlach, Frantisek Hartman, Ufuk Yilmaz, Ondrej Lukás, Mehmet Dogan, Mohamed Mandouh, Marios Fragkoulis, Asterios Katsifodimos
Proc. VLDB Endow.9