A Developer's Journey From Monoliths to Microservices

Microservices are the current "big thing" and most of the current technologies seems to be a fit for greenfield projects. Unfortunately the great majority of the developers can't build something from scratch - but that shouldn't prevent them to touch the world of microservices while dealing with their legacy monolith.

Come to this session to check how we are refactoring a Java EE monolith to a Microservices Architecture: our work done and the planned steps. Because enterprise development is not just a "hello world" application: it's a journey. We'll discuss the architectural decisions, requirements and implications. And of course we've plenty of code and deployments in a DevOps-enabled platform!

Transcript

1. A Developer's Journey From Monoliths to Microservices Edson Yanaga Director of Developer Experience @yanaga
2. Join developers.redhat.com 2 Java Champion Microsoft MVP
3. “Now, every company is a software company” — Forbes
4. Join developers.redhat.com 4
5. Software is made by people for people
6. Legacy
7. Any code delivered into production is Legacy
8. Feedback Loop
9. Join developers.redhat.com 9 Context
10. What is preventing you from delivering faster?
11. Bugs Testing Integration problems Continuous Integration Manual Deployment Continuous Delivery Integration problems again Microservices
12. We’re scaling people, not software
13. We’re solving integration issues by reducing the context to a cohesive Microservice
14. Conway’s Law
15. Join developers.redhat.com “organizations which design systems (…) are constrained to produce designs which are copies of the communication structures of these organizations.” 15
16. Join developers.redhat.com 16 “Two Pizza Rule” — Jeff Bezos
17. How do I run my Microservices?
18. PaaS
19. Buy or Build?
20. Join developers.redhat.com 20
21. Join developers.redhat.com 21
22. How do I begin my journey?
23. Join developers.redhat.com Strangler Application 23
24. Domain-Driven Design Bounded Contexts
25. Join developers.redhat.com 25
26. Join developers.redhat.com 26
27. Join developers.redhat.com 27 Wildfly Swarm Spring Boot Node.js
28. Join developers.redhat.com API Gateway 28
29. Join developers.redhat.com 29
30. Join developers.redhat.com 30 API Gateway
31. “reliability must come from software” — Jeff Dean (Google)
32. Join developers.redhat.com Design for Failure 32
33. Join developers.redhat.com 33 Circuit Breaker Bulkhead
34. Smart Routing
35. Join developers.redhat.com Synchronous or Asynchronous? 35
36. HTTP/REST or Message Broker?
37. Join developers.redhat.com What about reporting? 37
38. CRUD & CQRS
39. Join developers.redhat.com 39 CRUD (Create, Retrieve, Update, Delete) Write Operations Read Operations
40. Join developers.redhat.com 40 CQRS (Command Query Responsibility Segregation) Write Operations Read Operations
41. Join developers.redhat.com 41 http://teiid.jboss.org
42. http://debezium.io
43. Remember? It’s a journey
44. And we are taking the first steps
45. Want to follow the path? Join developers.redhat.com
46. plus.google.com/+RedHat linkedin.com/company/red-hat youtube.com/user/RedHatVideos facebook.com/redhatinc twitter.com/RedHatNews Thank you!