Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Sign up for free
Menu
Search
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Pricing
Search
Sign in
Sign up for free
Smash the Monolith: Refactoring Rails Apps with...
Search
Coraline Ada Ehmke
July 21, 2013
Technology
1.2k
8
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
Smash the Monolith: Refactoring Rails Apps with Services and APIs
Coraline Ada Ehmke
July 21, 2013
Transcript
94 slides
Smash the Monolith Refactoring Rails Applications
The ‘A’ Word
The definition, composition, and interactions of parts of a system.
Software architecture is...
A compromise between viability and perfection. Software architecture is...
Tempered by the need to deliver a solution. Software architecture
is...
Some science. Lots of aesthetics. Software architecture is...
Software architecture is...
vs. An age-old conflict... Big Up-Front Design Cowboy Coding
Then: Big Up-Front Design
Advantages Long-term product roadmaps Rich design artifacts Guided evolution Predictability
Disadvantages Slow implementation Resistance to change New feature friction No
room for mistakes
Now: Ad-Hoc Architecture
Guiding Principles Convention over configuration Discrete MVC layers Good separation
of concerns RESTful and resourceful
The Best Intentions Test-driven development + pair programming + pull
requests + code reviews = emergent design
The Best Intentions
Non-CRUD controller methods. The Road to Hell
Logic leaking into controllers and views. The Road to Hell
Complex object graphs. The Road to Hell
/lib/ becomes a junk drawer. The Road to Hell
Undocumented gem dependencies. The Road to Hell
Bloated user model. The Road to Hell
Signs of a Degraded Design Rigidity
Signs of a Degraded Design Fragility
Signs of a Degraded Design Immobility
Signs of a Degraded Design Feature friction
Change Gets Harder Over Time Relatively Easy Delegate If Possible
Take a Sick Day KILL IT WITH FIRE Difficulty of Change Time
How did we get here?
How did we get here? Dozens of hands on the
code.
How did we get here? Classes naturally attract new methods.
How did we get here? Increasingly slow test suite.
How did we get here? Entropy.
How did we get here? One line of code at
a time.
“Most software eventually degrades to the point where someone will
declare the design to be unsound.” Uncle Bob Martin
Values-Driven Development
Things We Value Fresh ideas combined with best practices.
Things We Value Solid design principles applied in novel ways.
A Values-Based Approach Culture of innovation + best practices +
solid design principles = better architecture?
Hexagonal Design
Theoretical Backing Layered architectures break down in practice.
Domain Objects HTTP Command Line Testing Messaging Persistence Monitoring Sinatra
Cron Test Unit Beanstalkd Postgres Honey Badger Rails Rake RSpec Rabbit MongoDB New Relic
Design Considerations Design for all of your users, not just
the obvious ones.
Design Considerations Give every class its own distinct API.
Design Considerations Write your application in pure Ruby.
Theoretical Backing Achieve framework independence.
Using APIs & Messages
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, Bell Labs CSRC HTTP
Design Considerations Implement an ecosystem of small applications.
Design Considerations Divide models between the applications.
Design Considerations Persistence is a service.
Design Considerations Bind applications together using APIs and messaging.
Design Considerations Determine a caching strategy.
Design Considerations Pick a messaging solution.
Rethinking Architecture
Roots Rock.
A Sudden Revelation What if we think of an application...
...as just another object?
Object-Oriented Architecture
Theoretical Backing Apply OO design principles to the architecture itself.
Classes communicating via messages Applications communicating via APIs & queues
! Theoretical Backing
Applying OO Principles An application is a group of components
that perform tasks on the same data.
Applying OO Principles An application should do one well-defined thing.
Applying OO Principles APIs allow us to easily extend our
interfaces.
Applying OO Principles It doesn’t matter what application sends, receives
or processes our messages.
Applying OO Principles APIs and presenters allow us to easily
create client-specific interfaces.
Legacy Applications
What is a legacy app? Age is not measured in
months or years or versions.
What is a legacy app? Legacy code is not broken.
What is a legacy app? Don’t git blame.
What is a legacy app? A storehouse of information about
a problem space.
Refactoring Tactics Dismantle god classes.
Refactoring Tactics Extract behaviors into modules.
Refactoring Tactics Extract models and business logic into engines.
Refactoring Tactics Migrate engines into discrete applications.
Refactoring Tactics Implement observers using a messaging service.
Refactoring Tactics Provide persistence through asynchronous services.
Refactoring Tactics Direct calls between applications rely on a good
set of APIs.
Refactoring Tactics Use your API as a guide to refactoring
your models.
Synchronous Calls via APIs Credentials Auth Token Auth Service Client
App
Asynchronous Calls via Message Queues Prefs Update Client App Attr
Change Persistence Service
Refactoring Tactics Find functional edges and refactor them into services.
Refactoring Tactics Make liberal use of the presenter pattern.
A declarative framework useful for building APIs. faceted.rb
On the Other Side of Refactoring
A Small App Ecosystem Consumer App Internal App 1 Internal
App 2 Persistence API Messaging API Reporting API Dashboard App
Reap the Benefits Reduced cost of change.
Reap the Benefits Support for unexpected and novel use cases.
Reap the Benefits Reduction of ceremony around releases.
Reap the Benefits Low-impact downtime.
Reap the Benefits Short ramp-up time for new developers.
Reap the Benefits Increased performance of test suites.
Reap the Benefits A/B testing on applications and infrastructure.
Reap the Benefits Greater flexibility.
Reap the Benefits Democratization of application architecture.
Go smash your monolith.
smashthemonolith.com Corey Ehmke @bantik
More Decks by Coraline Ada Ehmke
See All by Coraline Ada Ehmke
Scaling the Artisan
bantik
0
200
Your First Legacy Codebase
bantik
1
480
Alchemy and the Art of Software Development
bantik
0
390
Artisans and Apprentices
bantik
1
590
Lightweight BI with Ruby, Rails, and MongoDB
bantik
6
2.8k
Better Living Through Open Source
bantik
2
200
Lightweight Business Intelligence in Ruby
bantik
3
1.2k
Beautiful APIs with Faceted
bantik
3
390
Other Decks in Technology
See All in Technology
AIネイティブ組織の作り方。1人のPOとAIから始める、自社での実験
ama_ch
2
1.3k
OWASP AI Agentic Top10に準拠するクラウドネイティブなガードレールの実践(CNDW 2026)
keitah
1
390
AI×アジャイルで、石橋を高速で叩きながら渡る~電力会社がゼロから築いた会員サイト改善プロセス~ / 20261112 Ayami Kanazawa & Shigeru Hirai
shift_evolve
PRO
1
110
Test Impact Analysis を武器に立ち向かう、AI 時代のテスト増加に対するヌーラボのアプローチ / getting-started-datadog-test-impact-analysis
k6s4i53rx
0
280
共通基盤の実装に Kotlin - Quarkus を選定した理由と採用したアーキテクチャ
nealle
1
150
落とし穴にハマってわかった 開発生産性を測るときに気をつけたいこと
munakata
3
480
AWS Client VPNの設定でハマったポイントとその過程での気づき
amarelo_n24
1
420
パスワードのない鍵で、 データを手元に置く
ginjihayashi
0
390
SORACOM × AWS IoT Core でSREする
butadora
0
120
クラウドでも使えるNetApp -現場目線での設計とクラウドバックアップの活用
ryutakondo
1
260
マネージャーをエスパーにしない マネジメントされる側から始める、働きやすい現場づくり
comi190327
1
840
セキュリティチームは どのコンテナイメージの脆弱性対応を優先すべきか 〜CISA新指針とSCCで作る脆弱性トリアージ〜
swdtkuy
0
230
Featured
See All Featured
Making the Leap to Tech Lead
cromwellryan
135
10k
Breaking role norms: Why Content Design is so much more than writing copy - Taylor Woolridge
uxyall
2
540
How STYLIGHT went responsive
nonsquared
100
6.4k
Typedesign – Prime Four
hannesfritz
42
3.2k
Conquering PDFs: document understanding beyond plain text
inesmontani
PRO
4
3.3k
Design in an AI World
tapps
1
390
Measuring & Analyzing Core Web Vitals
bluesmoon
9
1.1k
Tell your own story through comics
letsgokoyo
1
1.1k
B2B Lead Gen: Tactics, Traps & Triumph
marketingsoph
1
310
The agentic SEO stack - context over prompts
schlessera
0
1k
A brief & incomplete history of UX Design for the World Wide Web: 1989–2019
jct
2
570
Why Your Marketing Sucks and What You Can Do About It - Sophie Logan
marketingsoph
0
470