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.

Real production use: Reactive design for the manufacturing industry


Published on

Real production use: Reactive design for the manufacturing industry by Roland Kuhn

The Reactive Manifesto motivates the reactive tenets with large-scale systems that serve millions of users worldwide, needing exorbitant data size and bandwidth coupled with sub-second latencies. This presentation puts the spotlight on the other end of the spectrum: the systems that operate manufacturing processes and logistics are vital to a factory’s success. Data sizes and rates are easily manageable with today’s hardware, the top priority is absolute reliability. In these systems resilience is the prime motivator for loose coupling, elasticity is just a consequence. This presentation explains the architecture approach taken at Actyx and discusses the suitability of different patterns in this context, including some war stories.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Real production use: Reactive design for the manufacturing industry

  1. 1. Real production use: Reactive design for the manufacturing industry Dr. Roland Kuhn May 25, 2018
  2. 2. What is a factory?
  3. 3. What is a production system? ?
  4. 4. So what does a factory do?
  5. 5. machines tools labor consumables electricity input materials output materials waste Icons here and on following slides made by Freepik from
  6. 6. Most factories are small
  7. 7. Typical IT systems in factories ERP enterprise resource planning DMS document management (a.k.a. fileshare) BI business intelligence (a.k.a. Excel) CAQ computer-aided quality devices printers, scales, access control, storage, …
  8. 8. For context: What does Actyx do?
  9. 9. Enterprise Software Personnel MachinesDevices
  10. 10. Characteristic data sources Without machines: the opposite of Big Data! timescale datasize ERP per minute or per hour kilobytes DMS per day megabytes personnel per minute or per hour bytes devices per minute or per hour if used by humans bytes to megabytes machines per second bytes to megabytes
  11. 11. Architecture v1: microservices
  12. 12. CassandraLagom microservices
  13. 13. Cloud microservices: the good parts _ rock solid programming model _ excellent cloud services support _ standards for edge connectivity
  14. 14. Cloud microservices: the drawbacks _ it does not work while something is wrong with the network _ not all data are allowed to leave factory premises
  15. 15. Architecture v2: less servers, actually
  16. 16. postgresDevice management Azure SQL Data GW assets
  17. 17. Important patterns for a resilient mesh _ let it crash _ coordination-free replication wherever possible _ event-sourcing _ domain objects _ pull-based messaging instead of circuit breakers see also
  18. 18. use code jbeachrdp for 50% discount
  19. 19. Conclusion Loosening the coupling implies losing control. Not all cases should be handled by the system.
  20. 20. use code jbeachrdp for 50% discount
  21. 21. Actyx AG, Ridlerstraße 31b, 80339 Munich, Germany Unless otherwise indicated, all materials on these pages are copyrighted by Actyx AG. Reproduction, modification, storage in a retrieval system or retransmission, in any form or by any means, electronic, mechanical or otherwise, for reasons other than personal use, is strictly prohibited without prior written permission. Factory Software Made Simple