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
520
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
240
Django Through The Years
andrewgodwin
0
130
Writing Maintainable Software At Scale
andrewgodwin
0
370
A Newcomer's Guide To Airflow's Architecture
andrewgodwin
0
280
Async, Python, and the Future
andrewgodwin
2
580
How To Break Django: With Async
andrewgodwin
1
630
Taking Django's ORM Async
andrewgodwin
0
640
The Long Road To Asynchrony
andrewgodwin
0
570
The Scientist & The Engineer
andrewgodwin
1
660
Other Decks in Programming
See All in Programming
M5Stackボードの選び方
tanakamasayuki
0
210
CDKを活用した 大規模コンテナ移行 プロジェクトの紹介
yoyoyopg
0
250
ファーストペンギンBot @Qiita Hackathon 2024 予選
dyson_web
0
220
Re:PandasAI:生成AIがデータ分析業務にもたらすパラダイムシフト【増補改訂版】
negi111111
1
890
AWS認定資格を受験するにあたり、気づいたこと・実践していたことのまとめ
satoshi256kbyte
1
120
tsconfig.jsonの最近の新機能 ファイルパス編
uhyo
6
1.5k
RemixとCloudflare Stack におけるFile Upload
ossamoon
1
120
sqlcを利用してsqlに型付けを
kamiyam
0
240
Go製CLIツールGatling Commanderによる負荷試験実施の自動化
okmtz
3
690
WEBアプリケーションにおけるAWS Lambdaを用いた大規模な非同期処理の実践
delhi09
PRO
7
4k
コードレビューと私の過去と未来
jxmtst
0
240
ポケモンで考えるコミュニケーション / Communication Lessons from Pokémon
mackey0225
4
170
Featured
See All Featured
Speed Design
sergeychernyshev
22
470
Why Our Code Smells
bkeepers
PRO
334
57k
Code Review Best Practice
trishagee
62
16k
Statistics for Hackers
jakevdp
796
220k
5 minutes of I Can Smell Your CMS
philhawksworth
202
19k
Designing the Hi-DPI Web
ddemaree
279
34k
What's new in Ruby 2.0
geeforr
341
31k
How to Ace a Technical Interview
jacobian
275
23k
Let's Do A Bunch of Simple Stuff to Make Websites Faster
chriscoyier
504
140k
For a Future-Friendly Web
brad_frost
174
9.3k
Imperfection Machines: The Place of Print at Facebook
scottboms
264
13k
BBQ
matthewcrist
85
9.2k
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