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.

JavaBin Trondheim and Bergen: Let your microservices flow

388 views

Published on

Slides from my talk at JavaBin Trondheim and JavaBin/Bitshift Meetup Bergen about flows stretching across services boundaries in microservices - and how workflow engines can help. Code I used in the live demo (which was most of the talk) can be found here: https://github.com/berndruecker/flowing-retail-concept-java & https://github.com/berndruecker/camunda-spring-boot-amqp-microservice-cloud-example

Published in: Technology
  • Be the first to comment

  • Be the first to like this

JavaBin Trondheim and Bergen: Let your microservices flow

  1. 1. Let your microservices flow! bernd.ruecker@camunda.com With thoughts from http://flowing.io @berndruecker | @martinschimak
  2. 2. AT&T
  3. 3. Bounded context and microservices Bounded Contexts = Microservices Shop Payment ShippingInventory • Independent components • Independent deployments • Decoupling between components • Dedicated teams (to fight conways law) • Autonomy of technology decisions • No horizontal team boundaries • New DevOps paradigms
  4. 4. https://www.flickr.com/photos/12567713@N00/310639290
  5. 5. Increasing complexity of relation- ships
  6. 6. Events Bounded Contexts = Microservices Order placed Shop Payment Shipping Business Outputs / Domain Events Inventory Payment received Goods fetched Goods shipped
  7. 7. It is not SOA Bounded Contexts = Microservices Order placed Shop Payment Shipping Business Outputs / Domain Events Inventory Payment received Goods fetched Goods shipped „smart endpoints and dumb pipes”
  8. 8. Elastic Resilient Responsive Message-driven Value Form Means 4 traits of a reactive system, from http://reactivemanifesto.org/ The value of event- or message-driven systems
  9. 9. Microservices Domain Driven Design Event Driven & Reactive
  10. 10. Collaboration using eventflows Order placed Payment received Goods fetched Goods shipped InventoryPayment ShippingShop
  11. 11. Live coding
  12. 12. The 7 sins of workflow Zero-code suites Homegrown engine Granularity bloopers BPM monolith Stakeholders habitat violation Over engineering No engine Wrong engine Wrong usage http://blog.bernd-ruecker.com/
  13. 13. Bernd Rücker Consultant & Evangelist 10+ years workflow http://bernd-ruecker.com/ bernd.ruecker@camunda.com Co-founder Camunda http://camunda.org/
  14. 14. Avoid alarming by management attention
  15. 15. Support operations
  16. 16. Distributed systems
  17. 17. Hug your business stakeholders more often!
  18. 18. Next generation workflow technology?
  19. 19. Stateless engine + RDMS RDMS
  20. 20. New kid on the block https://zeebe.io/ Zeebe Broker Your application Binary (MsgPack) Support streaming & batching Client Horiziontally scalable Append only log / event sourcing
  21. 21. Code online: https://github.com/berndruecker Slides online: https://bernd-ruecker.com Blog: https://blog.bernd-ruecker.com Feedback: https://bernd-ruecker.com/feedback With thoughts from http://flowing.io @berndruecker | @martinschimak
  22. 22. Thank you!

×