a developer's journey from monoliths to microservices - edson yanaga
TRANSCRIPT
A Developer's Journey From Monoliths to Microservices
Edson Yanaga Director of Developer Experience @yanaga
“Now, every company is a software company” — Forbes
Software is made by people for people
Legacy
Any code delivered into production is Legacy
Feedback Loop
What is preventing you from delivering faster?
Bugs Testing
Integration problems Continuous Integration
Manual Deployment Continuos Delivery
Integration problems again Microservices
We’re scaling people, not software
We’re solving integration issues by reducing the context to a cohesive Microservice
Conway’s Law
Join developers.redhat.com
“organizations which design systems (…) are constrained to produce designs which are copies of the communication structures of
these organizations.”
15
How do I run my Microservices?
PaaS
Buy or Build?
How do I begin my journey?
Domain-Driven Design Bounded Contexts
“reliability must come from software” — Jeff Dean (Google)
Smart Routing
HTTP/REST or Message Broker?
Command Query Responsibility Segregation
(CQRS)
Join developers.redhat.com39
http://teiid.jboss.org
Remember? It’s a journey
And we are taking the first steps
plus.google.com/+RedHat
linkedin.com/company/red-hat
youtube.com/user/RedHatVideos
facebook.com/redhatinc
twitter.com/RedHatNews
Thank you!