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
Deploying, at an Unusual Scale
Search
Andrew Godwin
October 22, 2011
Programming
7
580
Deploying, at an Unusual Scale
A talk I gave at DjangoCon Europe 2011, about Epio's internal architecture at that point.
Andrew Godwin
October 22, 2011
Tweet
Share
More Decks by Andrew Godwin
See All by Andrew Godwin
Reconciling Everything
andrewgodwin
1
320
Django Through The Years
andrewgodwin
0
210
Writing Maintainable Software At Scale
andrewgodwin
0
440
A Newcomer's Guide To Airflow's Architecture
andrewgodwin
0
360
Async, Python, and the Future
andrewgodwin
2
670
How To Break Django: With Async
andrewgodwin
1
730
Taking Django's ORM Async
andrewgodwin
0
730
The Long Road To Asynchrony
andrewgodwin
0
660
The Scientist & The Engineer
andrewgodwin
1
770
Other Decks in Programming
See All in Programming
あまり知られていない MCP 仕様たち / MCP specifications that aren’t widely known
ktr_0731
0
230
ZeroETLで始めるDynamoDBとS3の連携
afooooil
0
150
SwiftでMCPサーバーを作ろう!
giginet
PRO
2
230
Vibe coding コードレビュー
kinopeee
0
420
物語を動かす行動"量" #エンジニアニメ
konifar
12
3k
Understanding Kotlin Multiplatform
l2hyunwoo
0
250
新しいモバイルアプリ勉強会(仮)について
uetyo
1
250
11年かかって やっとVibe Codingに 時代が追いつきましたね
yimajo
1
240
『リコリス・リコイル』に学ぶ!! 〜キャリア戦略における計画的偶発性理論と変わる勇気の重要性〜
wanko_it
1
220
MCP連携で加速するAI駆動開発/mcp integration accelerates ai-driven-development
bpstudy
0
280
Quality Gates in the Age of Agentic Coding
helmedeiros
PRO
1
120
Claude Code で Astro blog を Pages から Workers へ移行してみた
codehex
0
180
Featured
See All Featured
Optimizing for Happiness
mojombo
379
70k
Scaling GitHub
holman
461
140k
ReactJS: Keep Simple. Everything can be a component!
pedronauck
667
120k
The Success of Rails: Ensuring Growth for the Next 100 Years
eileencodes
46
7.5k
Code Review Best Practice
trishagee
69
19k
The Cost Of JavaScript in 2023
addyosmani
51
8.8k
Fight the Zombie Pattern Library - RWD Summit 2016
marcelosomers
234
17k
Bootstrapping a Software Product
garrettdimon
PRO
307
110k
KATA
mclloyd
32
14k
Responsive Adventures: Dirty Tricks From The Dark Corners of Front-End
smashingmag
251
21k
The Myth of the Modular Monolith - Day 2 Keynote - Rails World 2024
eileencodes
26
3k
Six Lessons from altMBA
skipperchong
28
3.9k
Transcript
Deploying, At An Unusual Scale Andrew Godwin http://www.flickr.com/photos/whiskeytango/1431343034/ @andrewgodwin
Hi, I'm Andrew. Serial Python developer Django core committer Co-founder
of ep.io
Hi, I'm Andrew. Serial Python developer Django core committer Co-founder
of ep.io Occasional fast talker
""Andrew speaks English like a machine gun speaks bullets."" Reinout
van Rees
We're ep.io Python Platform-as-a-Service Easy deployment, easy upgrades PostgreSQL, Redis,
Celery, and more
Why am I here? Our Architecture How we deploy Django
How varied Django deployments are
Our Architecture
Balancer Runner Runner Runner App 1 App 2 App 3
App 2 App 4 App 1 Databases File Storage Balancer
Oh My God, It's Full of Pairs Everything is redundant
Distributed programming is Hard
Hardware Real colo'd machines Linode EC2 (pretty unreliable) (pretty reliable)
(pretty reliable) IPv6 (as much as we can)
ØMQ We used to use Redis Everything now on ZeroMQ
Eliminates SPOF* * Single Point Of Failure. What a pointless acronym.
ØMQ Usage Redundant location-resolvers (Nexus) REQ/XREP for control messages PUSH/PULL
for stats, logs PUB/SUB for heartbeats, locking
Runners Unsurprisingly, these run the code SquashFS filesystem images Virtualenvs
per app UID & permission isolation, more coming
Logging/Stats All done asynchronously using ØMQ Logs to filesystem (chunked
files) Stats to PostgreSQL database, for now
Loadbalancers Intercept all incoming HTTP requests Look up hostname (or
suffix) HTTP 1.1 compliant
Databases Shared (only for PostgreSQL) Dedicated (uses Runner framework) PostgreSQL
9, damnit
Django in the backend We use the ORM extensively Annoying
settings fiddling in __init__
www.ep.io Runs on ep.io, just like any other app* Provides
JSON API, web UI * Well not quite - App ID 0 is special - but we're working on it
WSGI It's a standard, right?
WSGI It's a standard, right? Well, yes, and it works
fine, but it's not enough for serving a Python app
Static Files CSS, images, JavaScript, etc. Needs a URL and
a directory path
Python & Dependencies Mostly filled by pip/buildout/etc packaging apparently allows
version spec
Deploying Django It makes things consistent, right?
Settings Layouts Vanilla settings.py local_settings.py configs/HOSTNAME.py Many others...
Python Paths Project-level imports App-level imports apps/ directories
Databases If it's SQL, it's PostgreSQL Redis for key-value, MongoDB
soon Some things assume a safe network
HA (High Availability) Not terribly easy with shared DBs PostgreSQL
9's sensible warm standby Redis has SLAVEOF Possibly use DRBD for general solution
Backups High Availability is NOT a backup btrfs for consistent
snapshotting Archived remote syncs No access to backups from servers
Migrations No solution yet for migration/code sync We're working on
it...
Web serving It's not like it's important or anything
gunicorn Small and lightweight Supports long-running requests Pretty stable
nginx Even more lightweight Extremely fast Really, really stable
The Load Balancer Used to be HAProxy Rewritten to custom
Python daemon eventlet used for high throughput Can't use nginx, no HTTP 1.1 for backends
Celery See: Yesterday's Talk Slightly tricky to run many We
use Redis as the backend
Management Commands First off, run as subprocess Then, a custom
PTY module Now, run as pty-wrapping subprocesses
Some General Advice If you're crazy enough to do this
Messaging's Not Enough Having a state to check is handy
Why run one, when you can run two for twice
the price? Redundancy is good. Double redundancy is better.
Always expect the worst Hope you never have to deal
with it.
The more backups, the better. Make sure you have historical
ones, too.
Django is very flexible Sometimes a little too flexible...
Your real problems will emerge later Don't over-optimise up front
for everything
Questions? Andrew Godwin
[email protected]
@andrewgodwin