Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Microservices, Micro Operations? - Challenges of Microservice models at the operations level

Microservices, Micro Operations? - Challenges of Microservice models at the operations level

Dustin Huptas, Andreas Schmidt

Microservices gain a lot of attention and a rising footprint within the communities of developers and software architects. Promises of flexible architectures are in reach, especially with container-driven stacks such as Docker. A rising number of dependent services will also challenge operations teams in delivering a functional system. The talk introduces to some of these challenges and offers working solutions from the field of automation and service discovery.

F28d4f1634bce85c90b76b197b1413d4?s=128

Andreas Schmidt

February 12, 2015
Tweet

Transcript

  1. © 2015 Cassini Consulting Dustin Huptas Andreas Schmidt Microservices, Micro

    Operations? Challenges of Microservice models at the operations level
  2. 12th Feb. 2015 Micro Services, Micro Operations? 2

  3. 12.02.15 Cassini Consulting 3

  4. None
  5. 5 12.02.15 Cassini Consulting Cassini consulting #devops #linux #configmgt #virtualization

    #Containers #networking #ipv6 #security #deploy #run
  6. 6 12.02.15 Cassini Consulting Cassini consulting #devops #linux #configmgt #security

    #virtualization #Containers #networking #ipv6 Dustin @dhpts System Architecture, Networking, Dev‘ing the Ops
  7. 7 12.02.15 Cassini Consulting Cassini consulting #devops #linux #configmgt #security

    #virtualization #Containers #networking #ipv6 Andreas @aschmidt75 Infra-coding, #serverspec, #containers & security, #networking
  8. 8 12th Feb. 2015 Micro Services, Micro Operations? Physical Servers

    Virtual Servers Containers Dynamic Workloads Years Days to Months Hours to Days Msecs to Seconds
  9. 12th Feb. 2015 Micro Services, Micro Operations? 9 Usually local

    development/ test environment Single host, single network Mocked services
  10. 12th Feb. 2015 Micro Services, Micro Operations? 10 Usually local

    development/ test environment Single host, single network Mocked services Scaling of instances (failover+performance) Services instances scattered across different hosts Networking, Security, i.e. Firewalling Logging and Monitoring on a larger scale Stuff needs to be persisted Non-functional ReQuirements
  11. http://thenewstack.io/new-stack-mitchell-hashimoto-containers-no-containers-one- question-2015/ 11 12th Feb. 2015 Micro Services, Micro Operations?

  12. 12 12.02.15 Cassini Consulting Increasing Number of Services Discovery of

    Services Dependencies
  13. Number of services: 1

  14. Software Architecture Patterns are changing 14 12th Feb. 2015 Micro

    Services, Micro Operations?
  15. System Architecture Patterns are changing to adapt 15 12th Feb.

    2015 Micro Services, Micro Operations?
  16. The # of services are increasing 16 12th Feb. 2015

    Micro Services, Micro Operations? Year 1 Year 2 Year 3 Year 4
  17. https://www.flickr.com/photos/davebass5/8284615214/ „My name is service, micro service.“

  18. https://www.flickr.com/photos/tonyjcase/2864378286 “My name is service..“ “So what? Mine, too.“ “Yeah.

    And don‘t forget about me. Like always.“
  19. https://www.flickr.com/photos/tonyjcase/2864378286 A Bag Of services Multiple stages Teams deploy independently

    every other day
  20. https://www.flickr.com/photos/rieder91/6008439579 How to call? Deployments scaling Firewalling Logging Monitoring Sharing

    knowledge debugging Dependencies
  21. CREATE and APPLY PATTERNS Logging
 Monitoring
 Deployments
 Debugging Across all

    Services &
 Teams META model Documentation Knowledge Data Keep System Maintainable You build it, You run it DevOps
  22. 22 12th Feb. 2015 Micro Services, Micro Operations?

  23. 23 12th Feb. 2015 Micro Services, Micro Operations? 3 Services

    - handcrafted
  24. 24 12th Feb. 2015 Micro Services, Micro Operations? Scalability &

    Failover
  25. 25 12th Feb. 2015 Micro Services, Micro Operations? Scalability &

    Failover
  26. 26 12th Feb. 2015 Micro Services, Micro Operations? ENDpoints disappear

  27. 27 12th Feb. 2015 Micro Services, Micro Operations? MULTI-Version? V3

    V3 V4 V4
  28. 28 12th Feb. 2015 Micro Services, Micro Operations? Reachability

  29. 29 12th Feb. 2015 Micro Services, Micro Operations? Wiring baked

    inTO Proxying/LB Configuration Management Tool
  30. 30 12th Feb. 2015 Micro Services, Micro Operations? Solve Wiring

    With Appropriate Tools
  31. 31 12th Feb. 2015 Micro Services, Micro Operations? i.e. coreos/etcd

    consul K/V cluster i.e. confd,
 consul-template, .. Template engine Proxying i.e. haproxy Apps Infra i.e. 
 progrium/registrator
  32. 12.02.15 Cassini Consulting 32 Dependencies

  33. 33 12th Feb. 2015 Micro Services, Micro Operations? Internal Software

    dependencies Inter-Service dependencies @ build time @ run time
  34. 34 12th Feb. 2015 Micro Services, Micro Operations? Startup order

  35. 35 12th Feb. 2015 Micro Services, Micro Operations? Resilience Circuit

    Breaker
  36. 36 12th Feb. 2015 Micro Services, Micro Operations? Circuit closed?

    Queue Full? Execute call Fallback Response timeout Success ? COMPUTE Circuit STATE Latency OK? positive Response
  37. It moves to another level in your system Complexity does

    NOT go away
  38. Use helpers to DEAL with shifted complexiTY manifests as DEPENDENCIES

  39. DevOps Mindset

  40. 40 12th Feb. 2015 Micro Services, Micro Operations? UPFRONT Design

    Changing architecture in-between
  41. FULL Automation is key Application Configuration needs to be dynamic

    Configuration Management Tools for SERVERS
  42. Static wiring of components reaches END-OF-LIFE Ability to detect peers

    Dynamic Service Discovery
  43. 43 12th Feb. 2015 Micro Services, Micro Operations? Dependencies externalize

    Call Stack LATENCY Introduce Circuit breakers
  44. Tools and frameworks are moving FAST PATTERNS are importaNT

  45. Operational behaviour changes SHIFT to micro services introduces changes at

    multiple levels
  46. 46 12th Feb. 2015 Micro Services, Micro Operations? Microservices, Micro

    Operations? Make Services Smarter Meta Ops For the Service landscape Employ suitable Patterns
  47. Q & A

  48. Recommended reading http://www.simplicityitself.com/microservices-reactive/the-role-of-data-in-microservices/ http://highscalability.com/blog/2014/4/8/microservices-not-a-free-lunch.html https://rclayton.silvrback.com/failing-at-microservices http://www.simplicityitself.com/learning/getting-started-microservices/service- discovery-overview/ http://thenewstack.io/new-stack-mitchell-hashimoto-containers-no-containers-one- question-2015/ http://blogs.gartner.com/gary-olliffe/2015/01/30/microservices-guts-on-the-outside/

    http://jaxenter.de/artikel/entwicklung-betrieb-skalierbarer-architektur-178014 (DE) 48 12.02.15 Micro Services, Micro Operations?
  49. Cassini Consulting Dustin Huptas Andreas Schmidt Oberwallstraße 24 10117 Berlin

    Deutschland Alle Angaben basieren auf dem derzeitigen Kenntnisstand. Änderungen vorbehalten. Dieses Dokument von Cassini Consulting ist ausschließlich für den Adressaten bzw. Auftraggeber bestimmt. Es bleibt bis zur einer ausdrücklichen Übertragung von Nutzungsrechten Eigentum von Cassini. Jede Bearbeitung, Verwertung, Vervielfältigung und/oder gewerbsmäßige Verbreitung des Werkes ist nur mit Einverständnis von Cassini zulässig. 12.02.15 Micro Services, Micro Operations? 49