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
Centralising the right things
Search
Tom Booth
June 09, 2017
Technology
1
1.1k
Centralising the right things
Tom Booth
June 09, 2017
Tweet
Share
More Decks by Tom Booth
See All by Tom Booth
Painting in Clojure
tombooth
0
120
Using data and visualisation to improve government
tombooth
0
230
Other Decks in Technology
See All in Technology
Alpine.js を活用した Laravel MPA フロントエンド最適化戦略 / Alpine.js MPA
tzmfreedom
1
690
日本MySQLユーザ会ができるまで / making MyNA
tmtms
1
180
Javaの新しめの機能を知ったかぶれるようになる話 #kanjava
irof
3
4.7k
Go製のマイグレーションツールの git-schemalex の紹介と運用方法
shinnosuke_kishida
1
340
AWSにおけるサイバー攻撃の傾向と具体的な対策
yuobayashi
8
790
KCD Brazil '25: Enabling Developers with Dapr & Backstage
salaboy
1
110
移行できそうでやりきれなかった 10年超えのシステムを葬るための戦略 / phper-kaigi-2025-ryu
carta_engineering
0
670
パスキー導入の課題と ベストプラクティス、今後の展望
ritou
7
1k
Redefine_Possible
upsider_tech
0
160
リポジトリをまるっとAIに食わせるRepomixの話
yamadashy
0
240
RubyKaigi 2025でプロポーザルが初めて採択されるまでにやったこと
yuuu
1
270
SaaSプロダクト開発におけるバグの早期検出のためのAcceptance testの取り組み
kworkdev
PRO
0
150
Featured
See All Featured
jQuery: Nuts, Bolts and Bling
dougneiner
63
7.7k
Optimising Largest Contentful Paint
csswizardry
34
3.1k
Building a Scalable Design System with Sketch
lauravandoore
462
33k
Evolution of real-time – Irina Nazarova, EuRuKo, 2024
irinanazarova
6
610
Site-Speed That Sticks
csswizardry
4
450
Fight the Zombie Pattern Library - RWD Summit 2016
marcelosomers
233
17k
How to Ace a Technical Interview
jacobian
276
23k
Statistics for Hackers
jakevdp
797
220k
Keith and Marios Guide to Fast Websites
keithpitt
411
22k
Easily Structure & Communicate Ideas using Wireframe
afnizarnur
194
16k
Documentation Writing (for coders)
carmenintech
69
4.7k
Agile that works and the tools we love
rasmusluckow
328
21k
Transcript
@tombooth Centralising the right things Tom Booth
@tombooth
@tombooth tl;dr
@tombooth Build a central team to empower and support others
@tombooth Centralised Decentralised Re-centralised
@tombooth Centralised Decentralised Re-centralised
@tombooth
@tombooth We weren’t one business, we were compe>ng func>ons
@tombooth Protec>onism built through compe>>on
@tombooth
@tombooth Every 3 weeks, …
@tombooth
@tombooth Every 3 weeks, we had a wild ride of
forgoHen changes
@tombooth Opera>ons would get the blame for developer problems
@tombooth
@tombooth Why did their change break my code?
@tombooth Centrally provided tools were very poor
@tombooth GeLng features to our users was slow When we
were centralised,
@tombooth Change was complex because of poor design When we
were centralised,
@tombooth Func>onal ownership caused serious fric>on When we were centralised,
@tombooth Centralised Decentralised Re-centralised
@tombooth One team needs to own the whole service
@tombooth
@tombooth You have to embrace change
@tombooth Deploying con>nuously is beHer for users
@tombooth A team should own its own architecture and infrastructure
@tombooth
@tombooth Every team with their own direc>on, liHle shared
@tombooth Solving the same problems, in the same way with
different implementa>ons
@tombooth Opera>ng at larger scale requires deeper knowledge
@tombooth GeLng features to our users was slow When we
were centralised,
@tombooth Change is complex because of poor architecture When we
were centralised,
@tombooth Func>onal ownership caused serious fric>on When we were centralised,
@tombooth The same problems were being solved repeatedly When we
were decentralised,
@tombooth No-one has the complete picture When we were decentralised,
@tombooth We weren’t focusing on our users as much as
we should When we were decentralised,
@tombooth Centralised Decentralised Re-centralised
@tombooth Retain ownership in the service teams
@tombooth Iden>fy common paHerns in our infrastructure
@tombooth Support common paHerns with great tooling
@tombooth Always ask, how can we help each other?
@tombooth Give teams room to experiment, do what’s best for
them
@tombooth Outside impressions maHer
@tombooth
@tombooth Help our owners, investors and auditors understand our services
@tombooth Work together not apart
@tombooth Work together on architecture
@tombooth Work together on issues
@tombooth Work together on bugs in produc>on at 3am
@tombooth GeLng features to our users was slow When we
were centralised,
@tombooth Change is complex because of poor architecture When we
were centralised,
@tombooth Func>onal ownership caused serious fric>on When we were centralised,
@tombooth The same problems were being solved repeatedly When we
were decentralised,
@tombooth No-one has the complete picture When we were decentralised,
@tombooth We weren’t focusing on our users as much as
we should When we were decentralised,
@tombooth Build a central team to empower and support others