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

Microservices zur Architekturmodernisierung - JAX2016

Microservices zur Architekturmodernisierung - JAX2016

Vortrag bei der JAX 2016 in Mainz, wie und wann man Microservices zur Architekturmodernisierung einsetzen kann

Alexander Heusingfeld

April 19, 2016

More Decks by Alexander Heusingfeld

Other Decks in Programming


  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 Business Value?
  2. 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
  3. Monolith Copy B Module 2 Request Cascades Monolith Copy A

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

    3. call service instance Service Service 1. register service ("myself") & heartbeat
  5. Service 2 Frontend Switch Monolith Module 1 Service 3 Service

    4 Customer Request Service 5 Reverse Proxy
  6. 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
  7. An SCS contains its own 
 user interface, specific 

    business logic and 
 separate data storage
  8. The manageable domain specific scope enables the development, operation and

    maintenance of an SCS by a single team. Team 1 Team 2 Team 3
  9. To further minimize coupling 
 to other systems, synchronous remote

    calls inside the business logic should be avoided.
  10. 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
  11. Alexander Heusingfeld, @goldstift [email protected] https://www.innoq.com/people/alexander-heusingfeld Michael Vitz, @michaelvitz [email protected] https://www.innoq.com/people/michael-vitz

    innoQ Deutschland GmbH Krischerstr. 100 40789 Monheim am Rhein Germany Phone: +49 2173 3366-0 innoQ Schweiz GmbH [email protected] Gewerbestr. 11 CH-6330 Cham Switzerland Phone: +41 41 743 0116 www.innoq.com Offices in: Berlin Offenbach München https://www.innoq.com/en/talks/ Thank you! Questions? Comments?