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
Why You Shouldn't Write a Database
Search
benbjohnson
October 22, 2015
Technology
2
530
Why You Shouldn't Write a Database
Talk given at the October 2015 Denver Go meetup.
benbjohnson
October 22, 2015
Tweet
Share
More Decks by benbjohnson
See All by benbjohnson
Static Code Analysis Using SSA
benbjohnson
6
1.5k
Writing a High Performance Database in Go
benbjohnson
11
6.5k
Raft: The Understandable Distributed Consensus Protocol
benbjohnson
106
27k
Behavioral Analytics - Understanding the "why" and "how" of your users.
benbjohnson
9
1.9k
New Tech - Sky
benbjohnson
2
350
Behavioral Databases
benbjohnson
16
2.4k
Sky Analytics Pitch Deck
benbjohnson
0
550
Other Decks in Technology
See All in Technology
Oracle Database 23ai Overview
oracle4engineer
PRO
0
310
SONiCスイッチを商用サービスに入れてみた(三井情報株式会社)
sonic
0
190
CSPが提供しない、フレッツ網をつかった閉域接続サービス&データ持ち込みにつかえるサービス 3選
armaniacs
1
910
上手く活用すればコスト削減につながる、ONTAPの Temperature Sensitive Storage Efficiency (TSSE) の紹介
non97
0
220
Databricksのご紹介
taka_aki
1
280
Python Web UIフレームワークのススメ
terapyon
0
240
意義から考えるObservability入門 #srenext
stefafafan
2
820
シビックテックによる、社会と民主主義のアップデート
halsk
2
140
AWS でのクラウド時代のログ活用
itotsum
1
110
オブザーバビリティ研修実践編
biwashi
27
10k
OpenFOAM(自宅ではじめる流体解析)
kamakiri1225
0
150
[JSAI24]Task Success Prediction for Object Manipulation Based on Scene, Aligned, and Narrative Representations
keio_smilab
PRO
0
130
Featured
See All Featured
The Cost Of JavaScript in 2023
addyosmani
22
4k
How STYLIGHT went responsive
nonsquared
92
4.9k
Documentation Writing (for coders)
carmenintech
60
4k
GitHub's CSS Performance
jonrohan
1025
450k
Code Review Best Practice
trishagee
56
16k
The Brand Is Dead. Long Live the Brand.
mthomps
49
32k
10 Git Anti Patterns You Should be Aware of
lemiorhan
650
58k
The Language of Interfaces
destraynor
151
23k
How to name files
jennybc
65
94k
Git: the NoSQL Database
bkeepers
PRO
423
63k
ParisWeb 2013: Learning to Love: Crash Course in Emotional UX Design
dotmariusz
104
6.7k
Imperfection Machines: The Place of Print at Facebook
scottboms
261
12k
Transcript
Why You Shouldn’t Write a Database Ben Johnson
Let’s define “database”
low-level LevelDB, BerkeleyDB, LMDB
Direct interface to OS Files, pages, & blocks Responsible for
data integrity Typically key/value
high-level SQLite, MySQL, PostgreSQL, Mongo, InfluxDB, etc
Builds on low-level stores Rows, tables, indexes Interfaces with end
user Relational, document, time series
Me
SkyDB ReportifyDB BoltDB InfluxDB
There are n+1 reasons not to write a database
#1. High barrier to entry
How to write a database
None
legit
sorta, but not quite
seriously?
suggests using XML
nope
Available resources?
Research papers!
Research papers! Narrowly focused (indexing, storage, locks)
Research papers! High level (little or no code)
Research papers! Assumes a Ph.D
Read source code!
Read source code! MySQL >1M SLOC
Read source code! Even small databases are 10KLOC+
There is no Writing Databases 101
#2. Debugging Sucks
Bugs are catastrophic Cause corruption, loss of data integrity
Bugs are catastrophic Users with data loss are very unhappy
Find a good hex editor
Find a good hex editor (I use Hex Fiend)
None
This is not what a database looks like
None
THIS is what a database looks like
Debugging w/o data Users usually can’t release their data
#3. Tradeoffs
Users don’t understand tradeoffs
None
Read Optimized vs Write Optimized
CPU Bound vs IO Bound
https://gist.github.com/jboner/2841832
Features are liabilities It’s not if you have bugs, it’s
how many
#4. Limited Community
Very few people who have written a production database
TONS of people who will tell you why your database
sucks
Databases are hard
The End
The End (Just kidding!)
Not scared off yet?
Only 2 reasons to write a database:
#1. To learn
Data Integrity Indexing Isolation levels Recovery Prefetching Parser & Lexers
Replication Snapshotting Transactions Materialized View Referential Integrity Query Compilation Query Planning Query Optimization Serializability Write Ahead Log Memory Profiling Redo/Undo Log Snapshot Isolation Recovery Two-Phase Commit Quorums
#2. Gain efficiency (For a specific use case)
The more generic your database, the fewer assumptions you can
make
Go write a database!
The End @benbjohnson
Questions? @benbjohnson