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

Architekturmodernisierung mit SCS und Microserv...

Architekturmodernisierung mit SCS und Microservices

Alexander Heusingfeld

February 01, 2017
Tweet

More Decks by Alexander Heusingfeld

Other Decks in Technology

Transcript

  1. Just use Microservices > Everyone’s doing Microservices, so you should,

    too > Everything will be faster with Microservices > There are lots of interesting tools to play with, much more interesting than the boring business domain > With Microservices we’ll be more agile
  2. Just use Microservices > Everyone’s doing Microservices, so you should,

    too > Everything will be faster with Microservices > There are lots of interesting tools to play with, much more interesting than the boring business domain > With Microservices we’ll be more agile Business Value?
  3. Microservice Characteristics small each running in its own process lightweight

    communicating mechanisms (often HTTP) built around business capabilities independently deployable mininum of centralized management may be written in different programming languages may use different data storage technologies http://martinfowler.com/articles/microservices.html
  4. Service 2 Frontend Switch Monolith Module 1 Service 3 Service

    4 Customer Request Service 5 Reverse Proxy
  5. Monolith Copy B Module 2 Request Cascades Monolith Copy A

    Module 1 Module 3 Monolith Copy C Module 4 Customer Request
  6. Monolith Copy B Module 2 Request Cascades Monolith Copy A

    Module 1 Module 3 Monolith Copy C Module 4 avoid! Customer Request
  7. Service Service Discovery Client Service Registry 2. discover service instances

    3. call service instance Service Service 1. register service ("myself") & heartbeat
  8. Domain Architecture -Which boxes? -Use Cases -Semantics & Purpose Macro

    Architecture -What’s in between? -Protocols, Deployment …so we show the different levels of decisions…
  9. Domain Architecture -Which boxes? -Use Cases -Semantics & Purpose Macro

    Architecture -What’s in between? -Protocols, Deployment Micro Architecture -What’s inside? -Component internals …so we show the different levels of decisions…
  10. Steps for modularisation • identify domains • group teams by

    domain User Management Payment Product Management
  11. Steps for modularisation • identify domains • group teams by

    domain • agree on macro architecture User Management Payment Product Management
  12. Steps for modularisation • identify domains • group teams by

    domain • agree on macro architecture • focus delivery pipeline on end-to-end features User Management Payment Product Management
  13. Steps for modularisation • identify domains • group teams by

    domain • agree on macro architecture • focus delivery pipeline on end-to-end features • team decides migration approach case-by-case User Management Payment Product Management
  14. An SCS contains its own 
 user interface, specific 


    business logic and 
 separate data storage
  15. Every SCS brings its own data storage and with its

    redundant data depending on the context and domain.
  16. The manageable domain specific scope enables the development, operation and

    maintenance of an SCS by a single team. Team 1 Team 2 Team 3
  17. Summary > aim42 provides structure for software modernization > SCSs

    are a reasonable approach to Microservices > Not everyone who wants microservices is immediately capable to establish them
  18. Summary > aim42 provides structure for software modernization > SCSs

    are a reasonable approach to Microservices > Not everyone who wants microservices is immediately capable to establish them > Don’t overwhelm people, change one thing at a time
  19. Thank you! Questions? Comments? Alexander Heusingfeld, @goldstift [email protected] Michael Vitz,

    @michaelvitz [email protected] innoQ Deutschland GmbH Krischerstr. 100 40789 Monheim am Rhein Germany Phone: +49 2173 3366-0 innoQ Schweiz GmbH Gewerbestr. 11 CH-6330 Cham Switzerland Phone: +41 41 743 0116 www.innoq.com Ohlauer Straße 43 10999 Berlin Germany Ludwigstraße 180 E D-63067 Offenbach Germany Kreuzstr. 16 D-80331 München Germany https://www.innoq.com/en/talks/