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.

2

Share

Download to read offline

Continously delivering containerized microservices

Download to read offline

Let’s have some fun while we entertain the idea that maybe - just maybe! - a microservice architecture would be a great fit for our (next) project. After all, we're almost past the microservices hype. It's time to prove that this can work!

Starting from the premise that a microservice architecture is only viable if we focus not only on the speed of change, but also improve the safety of change, we can learn a lot from the early adopters who have already scouted large parts of the unknown territory before us. Tools and platforms are maturing pretty fast too, so it’s safe to assume that we are now (almost) past the peak of impediments. Let’s start enjoying those microservices!

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all

Continously delivering containerized microservices

  1. 1. MATTHIAS NOBACK @matthiasnoback Continuouslydeliveringcontainerized,highlyavailable serviceswithpropercontextboundariesandmessaging integration,deployedtoserversinthecloud
  2. 2. Livingtheopensourcedream
  3. 3. PostponeJudgement!
  4. 4. WhatIsA Microservice?
  5. 5. MonolithVs Microservices
  6. 6. TheMonolith
  7. 7. Microservices
  8. 8. "Micro"?
  9. 9. PEOPLE WHO ARE CRITICAL OF MICROSERVICES PEOPLE WHO HAVE BUILT A MICROSERVICE SYSTEM
  10. 10. Perceivedproblems SCEPTICISM
  11. 11. BoundedContexts
  12. 12. MaximizeService Autonomy
  13. 13. TechnologyCircus
  14. 14. Standards,Standard Languages,Libraries,Etc.
  15. 15. StartSmall
  16. 16. TheToolsAreThere
  17. 17. LearnOnTheJob
  18. 18. Even in a small team, microservices can be a good choice of architecture. (my hypothesis)
  19. 19. Microservicearchitecture SHAKE OUT ALL THE PROBLEMS OF YOUR ORGANIZATION WITH A
  20. 20. RequiresAndEnables ContinuousDelivery
  21. 21. WhatIsContinuous Delivery?
  22. 22. Quality Testability Automation
  23. 23. ChangeBecomesFast AndSafe
  24. 24. IfItHurts,DoItOften
  25. 25. HelpsBuildADevops Culture
  26. 26. WhatIsDevops?
  27. 27. ToolsAreGettingBetter EveryDay
  28. 28. RequiresProper BoundedContexts
  29. 29. A natural, technical limit imposed on the domain model really helps for modularization (previous approaches have almost never worked) Eric Evans (paraphrased)
  30. 30. RequiresAndEnables TeamAutonomy
  31. 31. ReduceBottlenecks
  32. 32. Addedbenefits BUT BESIDES THAT?
  33. 33. Throw-AwayServices
  34. 34. Rewrite
  35. 35. Experiment
  36. 36. Polyglot
  37. 37. InnovateFaster
  38. 38. YouWillBePopular
  39. 39. http://leanpub.com/microservices-for-everyone/c/tilburg Questions?
  • DavidVanGompel1

    Jun. 14, 2017
  • MarcoMasotti

    Jun. 14, 2017

Let’s have some fun while we entertain the idea that maybe - just maybe! - a microservice architecture would be a great fit for our (next) project. After all, we're almost past the microservices hype. It's time to prove that this can work! Starting from the premise that a microservice architecture is only viable if we focus not only on the speed of change, but also improve the safety of change, we can learn a lot from the early adopters who have already scouted large parts of the unknown territory before us. Tools and platforms are maturing pretty fast too, so it’s safe to assume that we are now (almost) past the peak of impediments. Let’s start enjoying those microservices!

Views

Total views

572

On Slideshare

0

From embeds

0

Number of embeds

150

Actions

Downloads

2

Shares

0

Comments

0

Likes

2

×