Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Developing And Deploying Cloud-Native Apps As Resilient Microservices Architectures (Edson Yanaga)


Published on

You've been hearing about microservices for months and have probably taken a look at 12-factor and cloud-native apps, too. But there's a myriad of frameworks and tools you can use to craft your software and join the pieces together into a microservices architecture. You want to use the best tool for the job, and you need a hassle-free DevOps pipeline to orchestrate and deploy all of them. In this session, you'll learn how to combine a lot of different technologies and tools in a live demo that will open your eyes to the huge possibilities that microservices can help you achieve. We'll have it all: containers, Docker, Wildfly Swarm, Spring Boot, NodeJS, .NET, OpenShift, Jenkins, Kubernetes, and more.

Published in: Software
  • Be the first to comment

Developing And Deploying Cloud-Native Apps As Resilient Microservices Architectures (Edson Yanaga)

  1. 1. Developing and deploying cloud-native apps as resilient microservices architectures Edson Yanaga Director of Developer Experience @yanaga
  2. 2. Join developers.redhat.com2 Java Champion Microsoft MVP @yanaga
  3. 3. “Now, every company is a software company” — Forbes
  4. 4. Join developers.redhat.com4
  5. 5. “The two most important days in your life are the day you are born and the day you find out why.” — Mark Twain
  6. 6. Software is made by people for people
  7. 7. Legacy
  8. 8. Any code delivered into production is Legacy
  9. 9. Feedback Loop
  10. 10. Join developers.redhat.com10 Context
  11. 11. What is preventing you from delivering faster?
  12. 12. Bugs Testing Integration problems Continuous Integration Manual Deployment Continuos Delivery Integration problems again Microservices
  13. 13. We’re scaling people, not software
  14. 14. Distributed Systems are hard, but so are people
  15. 15. We’re solving integration issues by reducing the context to a cohesive Microservice
  16. 16. Conway’s Law
  17. 17. Join “organizations which design systems (…) are constrained to produce designs which are copies of the communication structures of these organizations.” 17
  18. 18. Join developers.redhat.com18 “Two Pizza Rule” — Jeff Bezos
  19. 19. Self-contained
  20. 20. Self-contained Teams
  21. 21. How do I run my Microservices?
  22. 22. PaaS
  23. 23. Buy or Build?
  24. 24. Join developers.redhat.com24
  25. 25. Join developers.redhat.com25
  26. 26. How do I begin my journey?
  27. 27. Join Strangler Application 27
  28. 28. Domain-Driven Design Bounded Contexts
  29. 29. Join developers.redhat.com29
  30. 30. Join developers.redhat.com30
  31. 31. Join developers.redhat.com31 Wildfly Swarm Spring Boot Node.js
  32. 32. Join API Gateway 32
  33. 33. Join developers.redhat.com33
  34. 34. Join developers.redhat.com34 API Gateway
  35. 35. “reliability must come from software” — Jeff Dean (Google)
  36. 36. Join Design for Failure 36
  37. 37. Join developers.redhat.com37 Circuit Breaker Bulkhead
  38. 38. Smart Routing
  39. 39. Blue/Green Deployment A/B Testing Canary Deployments Specific debugging and tracing
  40. 40. Remember? It’s a journey
  41. 41. And we are taking the first steps
  42. 42. Want to follow the path? Join
  43. 43. Thank you!