[PHPSP] Hexagonal Architecture

@camposmilaa hexagonal architecture

@camposmilaa Desenvolvedora ruby na Creditas Organizadora do Rails Girls Organizadora
do Women Dev Summit Camila Campos

@camposmilaa

@camposmilaa Why?

@camposmilaa “we need to release this soon, let’s do it
anyhow! we can clean it up later...” - every dev I know

@camposmilaa “the fact is that making messes is always slower
than staying clean.” - Uncle Bob

@camposmilaa architecture

@camposmilaa a good architecture screams software intention

@camposmilaa

@camposmilaa clean architecture

@camposmilaa

@camposmilaa core application

@camposmilaa core application adapters

@camposmilaa core application adapters external world

@camposmilaa ports and adapters

@camposmilaa

@camposmilaa what’s the idea?

@camposmilaa framework independent

@camposmilaa framework independent ui independent

@camposmilaa framework independent ui independent database independent

@camposmilaa framework independent ui independent database independent independent of any
external agents

@camposmilaa framework independent ui independent database independent independent of any
external agents easily testable

@camposmilaa the rules

@camposmilaa 1. the layers are everything

@camposmilaa core application adapters external world domain rules (entities) application
rules (use cases)

@camposmilaa core application adapters external world database web mailers async
jobs integrations

@camposmilaa core application adapters external world controller presenters gateways

@camposmilaa 2. dependencies should only go inwards

@camposmilaa external world

@camposmilaa external world database

@camposmilaa external world web

@camposmilaa external world framework

@camposmilaa external world scheduled job

@camposmilaa external world terminal

@camposmilaa

@camposmilaa ubiquitous language

@camposmilaa ubiquitous language customer

@camposmilaa ubiquitous language user customer

@camposmilaa ubiquitous language customer customer

@camposmilaa use cases entities

@camposmilaa entities - what the system is customer - document
number - name - birth date

@camposmilaa entities - what the system is address - street
- number - city

@camposmilaa entities - what the system is product - name
- price

@camposmilaa entities - what the system is order - ordered
at

@camposmilaa entities - what the system is buyer

@camposmilaa entities - what the system is item - quantity
- price

@camposmilaa entities - what the system is are

@camposmilaa entities - what the system is ADD ITEM +
product + quantity + buyer

@camposmilaa entities - what the system is

@camposmilaa use cases or interactors - what the system does
create ask for refund ship check fraud risk

@camposmilaa create order input - customer data - shipping address
- payment data flow 1. customer requests order creation 2. system validates given data 3. system creates order and define order id 4. system given order id back to the customer

@camposmilaa adapters

@camposmilaa adapters presenter controller use case interactor control flow external
world

@camposmilaa

@camposmilaa what about the dependency rule?

@camposmilaa adapters - dependency inversion principle (DIP) presenter controler use
case input port use case output port use case interactor control flow I I

@camposmilaa adapters - dependency inversion principle (DIP)

@camposmilaa wrapping up

@camposmilaa user requests resource

@camposmilaa user requests resource controller json

@camposmilaa user requests resource request model controller translation

@camposmilaa user requests resource request model controller use case (interactor)
request model

@camposmilaa user requests resource request model controller entity entity aggregate
entity entity use case (interactor) domain service interaction

entity entity use case (interactor) domain service repository database persistency

entity entity use case (interactor) domain service repository database persistency dip

entity entity result model use case (interactor) domain service repository database translation

entity entity result model use case (interactor) domain service presenter repository database result model

entity entity result model use case (interactor) domain service presenter repository database result model dip

@camposmilaa user requests resource user gets resource back request model
controller entity entity aggregate entity entity result model use case (interactor) domain service presenter repository database json

@camposmilaa just a thought...

@camposmilaa “the only way to go fast, is to go
well.” - Uncle Bob

@camposmilaa thanks! [email protected] @camposmilaa bit.ly/phpsp-hexagonal

@camposmilaa Interesting Links https://8thlight.com/blog/uncle-bob/2012/08/13/the-clean-architecture.html https://8thlight.com/blog/uncle-bob/2011/09/30/Screaming-Architecture.html http://alistair.cockburn.us/Hexagonal+architecture http://blog.mattwynne.net/2012/05/31/hexagonal-rails-objects-values-and-hexagons/ https://spin.atomicobject.com/2013/02/23/ports-adapters-software-architecture/ http://five.agency/android-architecture-part-3-applying-clean-architecture-android/ http://tidyjava.com/clean-architecture-screaming/
Domain Driven Rails by Yan Pritzker https://vimeo.com/106759024 Clean Architecture by Uncle Bob https://www.youtube.com/watch?v=Nltqi7ODZTM Clean Architecture and Desing by Uncle Bob https://www.youtube.com/watch?v=Nsjsiz2A9mg Hexagonal Rails by Matt Wynne https://www.youtube.com/watch?v=CGN4RFkhH2M Clean Architecture: A Craftsman's Guide to Software Structure and Design by Uncle Bob (Livro)

[PHPSP] Hexagonal Architecture

[PHPSP] Hexagonal Architecture

More Decks by Camila Campos

Other Decks in Programming

Featured

Transcript