Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Building a streaming database service
Search
Sponsored
·
Ship Features Fearlessly
Turn features on and off without deploys. Used by thousands of Ruby developers.
→
Siddharth Kothari
May 21, 2015
Technology
230
1
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
Building a streaming database service
Streaming Queries with ElasticSearch
Siddharth Kothari
May 21, 2015
More Decks by Siddharth Kothari
See All by Siddharth Kothari
Data Streams with Elasticsearch
siddharthlatest
0
140
Appbase.io - Customer Deck
siddharthlatest
0
140
Appbase.io - Investor Deck
siddharthlatest
0
340
Meteor Talk: Building Mitter
siddharthlatest
1
110
Data Streams on ElasticSearch
siddharthlatest
0
160
Appbase - A realtime events-based document store
siddharthlatest
1
850
Scalability Best Practices
siddharthlatest
0
200
Other Decks in Technology
See All in Technology
少人数データチームのDevin活用実践事例
runandy16
2
440
全員がプロダクトへ向き合う組織を持続成長させるために——組織づくりのフライホイールと4象限 / The Flywheel Model and Four Quadrants for Organizational Design
hiro_torii
3
820
[RSJ26] AnoleVLA: Lightweight Vision-Language-Action Model with Deep State Space Models for Mobile Manipulation
keio_smilab
PRO
0
120
AI時代におけるプロダクト横断勉強会の設計
zozotech
PRO
0
150
いかに伝えるか 〜新卒エンジニアの教育のための、ライトノベル活用の一例
ikedon
1
190
bet_ai_day_2026_session02
agenticsec
1
970
ブラウザアプリの継続的パフォーマンスモニタリング (序) / Continuous Browser Application Performance Monitoring; Act 1
moznion
0
110
[RSJ26] Building a VLA Model Based on Self-Distilled Classification
keio_smilab
PRO
0
190
Bet AI Day 2026丨Agentは、「金融」という巨大産業の何を変えられるのか
layerx
PRO
0
760
【Oracle AI Spotlight ウェビナー】AWSか、Azureか、Google Cloudか。その議論にオラクルを含める意義。
oracle4engineer
PRO
2
230
Bet AI Day 2026丨AIによって本質に戻るシステムリスク管理
layerx
PRO
0
870
「重なり」は迎える側がつくる ― 人もAIエージェントも歓迎するプロダクトエンジニアリング ―
go0517go
PRO
0
230
Featured
See All Featured
Effective software design: The role of men in debugging patriarchy in IT @ Voxxed Days AMS
baasie
0
510
We Have a Design System, Now What?
morganepeng
55
8.3k
Digital Projects Gone Horribly Wrong (And the UX Pros Who Still Save the Day) - Dean Schuster
uxyall
1
2.7k
コードの90%をAIが書く世界で何が待っているのか / What awaits us in a world where 90% of the code is written by AI
rkaga
63
45k
Rails Girls Zürich Keynote
gr2m
96
14k
Public Speaking Without Barfing On Your Shoes - THAT 2023
reverentgeek
1
560
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
141
35k
Leveraging Curiosity to Care for An Aging Population
cassininazir
1
490
svc-hook: hooking system calls on ARM64 by binary rewriting
retrage
2
550
Improving Core Web Vitals using Speculation Rules API
sergeychernyshev
21
1.6k
Why You Should Never Use an ORM
jnunemaker
PRO
61
10k
Stewardship and Sustainability of Urban and Community Forests
pwiseman
0
510
Transcript
Streaming @siddharthlatest
The title could also be: * Streaming Queries with ElasticSearch
* Streaming DBs will take over the world * What the heck is a streaming database?
Siddarth, sith in making Co-founder and CEO, appbase.io Give me
a shout at @siddharthlatest GET /programming/stacktrace [“Games”, “C”, “Python”, “Java (sigh) ”, “AI”, “JS”, “Databases”]
Streaming, like videos?! You see …
Not Video Streaming via Ben Rubin, CEO @ Meerkat
• live
Not just synchronous and 1:Many, but also: CRUD with structured
data
Topics: 1. What is a streaming database? 2. The use-cases
3. ElasticSearch as the query layer 4. Streaming Topology 5. How does it scale? 6. The future
Results as Streams
Results as Streams
1. Streams and Firehoses from #IoT 2. Monitoring Systems 3.
Analytics 4. E-commerce: Search, Price Monitoring Use-cases
Topics: 1. What is a streaming database? 2. The use-cases
3. ElasticSearch as the query layer 4. Streaming Topology 5. How does it scale? 6. The future
Elasticsearch Distributed Full-text Search based on Lucene Can scale to
many nodes and highly available Analytics, Document Oriented, Open Source
ES: Percolation aka Search in Reverse 1. Indexing a Query
2. Matches when new documents are added 3. Distributed design since v1.0.0
Not just synchronous and 1:Many, but also: CRUD with structured
data
An Example Snippet Registering a Query
Match a Document Response
Topics: 1. What is a streaming database? 2. The use-cases
3. ElasticSearch as the query layer 4. Streaming Topology 5. How does it scale? 6. The future
Streaming Topology • Queries are subscriptions (HTTP Streaming / Websockets)
• Publish matches to subscribers. • Works as is with the ES API.
Streaming Topology
Streaming Topology • Beyond Percolation, keep the document store model
of ES. • Every document is a topic, which can have references. • When a doc is created, updated, or deleted; notify all the docs that refer to it.
Streaming Workflows • Every document has an ES Path exposed
by REST. Endpoint Worker Push back to stream • Topology like Apache Storm, but you can notify the workers using the entire ElasticSearch API.
Topics: 1. What is a streaming database? 2. The use-cases
3. ElasticSearch as the query layer 4. Streaming Topology 5. How does it scale? 6. The future
How does it distribute, scale? • Underlying Store: ES is
highly available, can scale to many nodes. • Were able to ingest 100,000 documents per second on 20 C4.2x large nodes (AWS). • Eventually consistent, with a very small t. • Distributed Streaming Topology is a work in progress.
Looking forward “The web has moved to #realtime, why shouldn’t
the Backend Infrastructure too?” “DBs are moving to having RESTful APIs, percolators, streaming interfaces are the next steps”.
Bold claim “In three years, every modern DB will have
a streaming interface.”
@siddharthlatest