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
Designing systems to scale
Search
Michael Heap
October 06, 2012
Technology
1.6k
1
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
Designing systems to scale
Talk given at PHPNW12 in Manchester, England
Michael Heap
October 06, 2012
More Decks by Michael Heap
See All by Michael Heap
WTF are OKRs?
mheap
0
530
But why does the business care?
mheap
0
350
Advanced GitHub Actions
mheap
0
660
Controlling Your Kong Gateway With decK and CI/CD
mheap
0
680
API Standards 2.0
mheap
1
1.3k
API Standards 2.0
mheap
0
680
Dr Sheldon Cooper Presents: Fun with Flags (NEPHP)
mheap
0
770
Dr Sheldon Cooper Presents: Fun with Flags
mheap
0
1.2k
Behat for characterization tests
mheap
0
560
Other Decks in Technology
See All in Technology
サイバーエージェントにおけるAI推進戦略と変革への取り組み
shotatsuge
0
670
背中から、背中へ /paying forward to community
naitosatoshi
0
200
4人目のSREはAgent
tanimuyk
0
350
きのこカンファレンス2026_肩書きを外したとき私は誰か
yamasatimi
1
120
技術・能力を向上する原理原則 #きのこセッションa #きのこ2026
bash0c7
0
190
Multi-Agent並列開発を 安全に回すための技術 / Technology for Safely Multi-Agent Parallel Development
tooppoo
0
240
飲食店もAIで。レジ締めやハンディシステムをつくってる話 / Using AI for restaurant management
vtryo
0
220
40代で“やっとエンジニアになれた”――閉じた学びを開き、空の青さを知る / 20260628 Naoki Takahashi
shift_evolve
PRO
4
1.6k
なぜ人は自分のプロジェクトを 「なんちゃってアジャイル」と 自嘲するのか
kozotaira
0
230
アラート調査向けAIエージェントの本番導入とその後/AI Agents for Alert Investigation: Production Deployment and After
taddy_919
1
310
知見・人・API・DB・予算 ─ ナイナイ尽くしだった人事データ整備 with dbt、5年間の学び
ken6377
1
120
AIペネトレーションテスト・ セキュリティ検証「AgenticSec」紹介資料
laysakura
2
7.9k
Featured
See All Featured
Context Engineering - Making Every Token Count
addyosmani
9
1k
技術選定の審美眼(2025年版) / Understanding the Spiral of Technologies 2025 edition
twada
PRO
118
120k
Designing for Timeless Needs
cassininazir
1
270
RailsConf 2023
tenderlove
30
1.5k
The Art of Programming - Codeland 2020
erikaheidi
57
14k
Organizational Design Perspectives: An Ontology of Organizational Design Elements
kimpetersen
PRO
1
760
Facilitating Awesome Meetings
lara
57
7k
A Soul's Torment
seathinner
6
3k
JavaScript: Past, Present, and Future - NDC Porto 2020
reverentgeek
52
6k
[Rails World 2023 - Day 1 Closing Keynote] - The Magic of Rails
eileencodes
38
2.9k
Creating an realtime collaboration tool: Agile Flush - .NET Oxford
marcduiker
35
2.5k
JAMstack: Web Apps at Ludicrous Speed - All Things Open 2022
reverentgeek
1
490
Transcript
Designing Systems To Scale
I’m Michael
I’m @mheap I’m Michael
I’m absolutely terrified I’m @mheap I’m Michael
Designing Systems To Scale
Designing Systems To Scale
Designing Systems To Scale
Write programs that do one thing and do it well.
Write programs to work together. Write programs to handle text streams, because that is a universal interface. - Doug McIlroy
Do one thing, and do it well
None
V1
V1 • Codeigniter Application
V1 • Codeigniter Application • No (working) indices on the
database
V1 • Codeigniter Application • No (working) indices on the
database • Used the REST API and pulled data on demand
V1 • Codeigniter Application • No (working) indices on the
database • Used the REST API and pulled data on demand • PHP for realtime parsing
V1 • Codeigniter Application • No (working) indices on the
database • Used the REST API and pulled data on demand • PHP for realtime parsing • All stored in one git repo
24 Users
V1 • Codeigniter Application • No (working) indices on the
database • Used the REST API and pulled data on demand • PHP for realtime parsing • All stored in one git repo
V2
V2 • Decoupled
V2 • Decoupled • Made up of five “apps”
V2 • Decoupled • Made up of five “apps” •
Easier to scale
V2 • Decoupled • Made up of five “apps” •
Easier to scale • More fault tolerant
MySQL Twitter Redis API Bucket Parser API Website Mobile App
Do one thing, and do it well
... is rule #1
If all you have is a hammer...
... everything looks like a nail
Rule #2
Use the right tool for the job
LNMPNRM
LNMPNRM • Linux
LNMPNRM • Linux • nginx
LNMPNRM • Linux • nginx • MySQL
LNMPNRM • Linux • nginx • MySQL • PHP
LNMPNRM • Linux • nginx • MySQL • PHP •
NodeJS
LNMPNRM • Linux • nginx • MySQL • PHP •
NodeJS • Redis
LNMPNRM • Linux • nginx • MySQL • PHP •
NodeJS • Redis • Mongo DB
LNMPNRMR? • Linux • nginx • MySQL • PHP •
NodeJS • Redis • Mongo DB • Ruby
Rule #3
Stand on the shoulders of giants
Do one thing, and do it well Use the right
tool for the job Stand on the shoulders of giants
Now for the technical stuff...
Service Oriented Architecture
Shared Nothing Architecture
... Except your database
Make it stateless
Make it event driven
API Driven Design
Models talk to the Database
Models talk to the API
API = Data
Website
Mobile App
Raspberry Pi
API = Data
Things I’ve learned
Expose JSON
REST is good
REST is good Except when it’s not
Databases
We use MySQL
We use InnoDB
MySQL 5.6 EXPLAIN ALL THE THINGS!
None
pt-online-schema-change xtrabackup pt-archive pt-query-digest pt-query-advisor pt-show-grants pt-fingerprint
Things I’ve learned
Indexes go from left to right
User (email, first, last, dob) name_index(first, last) email_index(email) user_index(last, dob)
InnoDB uses primary key in indexes
Speed up SELECT Slow down INSERT Indices
One connection means One query
ORM’s are evil
Denormalisation is ok
Backups
mysqldump
InnoDB Hot Backup
Percona Xtrabackup
1,000,001
Recovery
Choose your battles
Servers
Servers (in the cloud?)
Learn to set up a server
Leave it to the professionals
Virtualisation
Get a VPS with Amazon AWS
Get a VPS with Rackspace
Get a VPS with Azure
Get a VPS with $vpsCompany
Leeds Hack
Things I’ve learned
£££
Multiple small beats one large
Dedicated is good too
Host your own database
Documentation
Not just about writing your own
None
You should also write your own
None
Easy Can we still deploy?
Easy Can we still deploy? Harder What if we need
a new server firing up?
Easy Can we still deploy? Harder What if we need
a new server firing up? Even Harder What if $customComponent breaks?
Make yourself dispensable
Always code as if the guy who ends up maintaining
your code will be a violent psychopath who knows where you live - John f. Woods
Things I’ve learned
Smart Defaults
Dependency Management
Just use Composer or rubygems/npm/pip... etc
Things I’ve learned
Lock your dependecies
v 1.4.2
v 1.4.2 Bug Fix
v 1.4.2 Feature release
v 1.4.2 All hell breaks loose
Lock your dependecies
Control your dependecies
None
Control your dependecies
Automation
Predictability
It saves time
Choose one [MRJC]ake
forever stop /home/user/parser/parser.js && APP_ENV=production forever start -a -l ~/parser-logs/
parser.log -o ~/parser-logs/out.log -e ~/parser-logs/ parser.err.log --minUptime 10000 --spinSleepTime 8000 ~/ parser/parser.js
forever stop /home/user/parser/parser.js && APP_ENV=production forever start -a -l ~/parser-logs/
parser.log -o ~/parser-logs/out.log -e ~/parser-logs/ parser.err.log --minUptime 10000 --spinSleepTime 8000 ~/ parser/parser.js parser_control restart
Automating scary things
Push data not pull
Things I’ve learned
Vagrant
Puppet/Chef
Devops!
Logging
Log *everything*
Aggregated logs
Monolog
Make it an option
Things I’ve learned
Nothing... yet
Outsourcing
Things like hosting repos
Things like sending emails
Things like *insert task*
Outsourcing validation
Things I’ve learned
You don’t have to do everything
Testing
Testing is for peace of mind
It is not a design process
Integration tests over unit tests
Unit tests are nice too
Things I’ve learned
Test only what you need
Behat + Selenium
Being Human
You’re your own worst enemy
Logging queries to MongoDB
Node.js’ process.nextTick
Something I haven’t even realised
Things I’ve learned
Learn to fail
People make mistakes
Believe in yourself
I’m Michael
I’m @mheap I’m Michael
I hope you enjoyed this talk I’m @mheap I’m Michael