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
Services, Architecture and Channels
Search
Andrew Godwin
April 03, 2017
Programming
4
600
Services, Architecture and Channels
A talk I gave at DjangoCon Europe 2017 in Florence, Italy
Andrew Godwin
April 03, 2017
Tweet
Share
More Decks by Andrew Godwin
See All by Andrew Godwin
Reconciling Everything
andrewgodwin
1
210
Django Through The Years
andrewgodwin
0
90
Writing Maintainable Software At Scale
andrewgodwin
0
330
A Newcomer's Guide To Airflow's Architecture
andrewgodwin
0
250
Async, Python, and the Future
andrewgodwin
2
540
How To Break Django: With Async
andrewgodwin
1
580
Taking Django's ORM Async
andrewgodwin
0
590
The Long Road To Asynchrony
andrewgodwin
0
520
The Scientist & The Engineer
andrewgodwin
1
580
Other Decks in Programming
See All in Programming
TypeScriptの型とパフォーマンス (TSKaigi 2024)
ypresto
14
4.6k
JavaScript Closure
asoluka
0
2k
Enjoy Creative Coding with Ruby (RubyKaigi2024)
chobishiba
0
710
GitHub Actionsの痒いところを埋めるサードパーティーランナー
dora1998
2
260
freeeのエンジニアが 就活で出そうな コーディングテストを 解説してみる
freee
1
170
RailsConf 2024: Riffing on Rails: sketch your way to better designed code
kaspth
1
220
Good first issues of TypeProf
mame
4
590
AmperとFleetを使ったAndroidアプリ
yoppie
0
300
CQRS meets modern Java
simas
PRO
2
480
mb_trim関数を作りました
youkidearitai
PRO
1
230
Prepare for Jakarta EE 11 - Performance and Developer Productivity
ivargrimstad
0
300
2024 コーディング研修
ckazu
2
660
Featured
See All Featured
Build your cross-platform service in a week with App Engine
jlugia
226
17k
Building Better People: How to give real-time feedback that sticks.
wjessup
356
18k
Web Components: a chance to create the future
zenorocha
306
41k
I Don’t Have Time: Getting Over the Fear to Launch Your Podcast
jcasabona
23
1.7k
[RailsConf 2023] Rails as a piece of cake
palkan
28
4.1k
Rails Girls Zürich Keynote
gr2m
91
13k
Clear Off the Table
cherdarchuk
86
310k
How GitHub (no longer) Works
holman
305
140k
Building a Modern Day E-commerce SEO Strategy
aleyda
22
6.5k
jQuery: Nuts, Bolts and Bling
dougneiner
60
7.2k
Designing for Performance
lara
601
67k
Done Done
chrislema
178
15k
Transcript
Andrew Godwin @andrewgodwin
Andrew Godwin Hi, I'm Django core developer Senior Software Engineer
at Apparently now does software architecture
The Monolith
The Monolith Only one version of any dependency Everything can
import everything Deployed all at once No separation Side-effects from other code
None
Services Code split up by purpose/team Defined cross-boundary API Deployed
separately Can use different versions of dependencies Isolated from each other
Why services?
Easier to manage Smaller, self-contained problems
Independent Scaling And easier performance analysis
Faster Individual Deployment Less to deploy at once
Complex Interdependencies Harder to deploy & track bugs
Requires great communication Teams need calling contracts and APIs
More points of failure Not just one set of homogenous
servers
No more quick hacks Separation forces a level of code
design
Switching To Services Or: How I Learned To Stop Worrying
And Love The Monolith
Identify the "cut points" You might need to make some
Allocate inventory Calculate Price & Charge card Finalise order Make
Order Row &
Make Order Row Allocate inventory Calculate Price Charge card Finalise
inventory Finalise order
Make Order Row Allocate inventory Calculate Price Charge card Finalise
inventory Finalise order
Define APIs between services Behave like all other teams are
third-party
Separate Datastores & Servers Make them as separate as possible
Communication & Transport
Service 2 Service 3 Service 1
Service 2 Service 3 Service 1 Direct Communication (20 services?
190 connections!)
Service 2 Service 3 Service 1 Direct with discovery Orchestrator
Service 2 Service 3 Service 1 Centralised Routing Router
Service 2 Service 3 Service 1 Message Bus
Centralised Comms Tradeoffs Distributed Comms Single point of failure Nasty
partial failures
At-least-once delivery Tradeoffs At-most-once delivery Some messages duplicated Some messages
lost
First-In-First-Out Tradeoffs First-In-Last-Out Easily backlogged Wide range of latencies
Channels & ASGI
Channel Layer Interface Server Worker Server Process 1 ASGI ASGI
Asynchronous socket handling Synchronous Django project Interface Server Worker Server ASGI ASGI Worker Server ASGI Process 2 Process 3 Process 4
Service 2 Service 3 Service 1 Channel Layer
Service Client inventory.request response.aF53Vds21
At-most-once delivery ASGI's Tradeoffs You have to design for potential
loss Low-latency but non-persistent Good for protocols, bad for important task queues Capacity, Backpressure and FIFO Informs producers quickly about pileups in the queue
Top Service-Oriented Architecture Tips
Per-request "correlation IDs" Track a set of service calls through
the stack
Feature Flag message headers Bundle them in, don't have every
service query them
Source Of Truth Each data model has a service that
owns (& caches) it
Metrics. Metrics everywhere. Both performance and network health
Design for failure Don't assume two things will both succeed
DO NOT START OFF WITH SERVICES Write separate Python libraries
instead
Thanks. Andrew Godwin @andrewgodwin