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.

Paremus servicefabric v1.14

32 views

Published on

Paremus Service Fabric 1.14 demonstration: polyglot container / Microservices; Java/OSGi applications; management of ZooKeeper ensembles; the Fabric's Epidemic discovery mechanisms; a simple IoT example using Eclipse sensiNact etc.

Demonstrations using both Cloud (AWS) and edge (physical laptop) resources. Also some supporting background. Operational Complexity, and use of Service Fabric for EU BRAIN-IoT Smart City & Industry4.0 use cases.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Paremus servicefabric v1.14

  1. 1. Copyright © 2005 - 2018 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved.November 2018 www.paremus.com for Cloud, Edge & Fog Computing Lightweight, Modular, Adaptive and Operationally Simple
  2. 2. Copyright © 2005 - 2018 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved.November 2018 2 “ Huston, we have a problem ”
  3. 3. Copyright © 2005 - 2018 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved.November 2018 3 Operation Complexity
  4. 4. Copyright © 2005 - 2018 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved.November 2018 4 Complexity
  5. 5. Copyright © 2005 - 2018 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved.November 2018 A pervasive problem faced by every Enterprise. But THE fundamental road-block for Smart Cities and Industry 4.0: ➡ orders of magnitude more sophisticated than traditional Enterprise IT! ➡ Requires localised in-situ compute. ➡ thousands, hundreds of thousands, maybe millions, of smart devices; these feeding into a complex and changing ecosystem of Software Services. ➡ Yet limited funds and small general purpose IT departments. Solutions MUST be: ➡ Operationally simple to manage & maintain at scale. ➡ Secure by Default ➡ Flexible, Adaptable & Evolvable. ➡ Decoupled from source Developers! DevOps won’t work. The Complexity Crisis! 5
  6. 6. Copyright © 2005 - 2018 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved.November 2018 6 ➡ Operationally Simple: To Install, Manage, Scale and Maintain. ➡ Type of Runtime: From lightweight Cloud Edge (e.g. ad-hoc or pervasive MicroCloud on Raspberry Pi’s / gateways), to your Cloud Core (physical or virtual compute resources). ➡ Application Support: From Legacy Applications, to modular Microservices, and beyond! ➡ Secure by Default: No reliance on internal or external DNS / Internet services. ➡ Governance & Provenance: At all times the pedigree of all software components is known. ➡ Open Industry Standards: The Paremus Service Fabric
  7. 7. Copyright © 2005 - 2018 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved.November 2018 7 Heard all this before?
  8. 8. Copyright © 2005 - 2018 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved.November 2018 8 Let’s Demonstration ➡ Creating a Service Fabric ➡ Polyglot Microservices ➡ Labels, Contracts & ZooKeeper Ensembles ➡ A modular Java / OSGi R7 example (https://enroute.osgi.org) ➡ Horizontal Scaling and Asynchronous Services ➡ The Modular IoT Cloud Edge ➡ More on Discovery and Hierarchy ➡ Pulling the pieces together … Fog, Smart City, Manufacturing / CPS (http://www.brain-iot.eu) What Smart City & Industry 4.0 customers really needs (and Enterprise too!)
  9. 9. Copyright © 2005 - 2018 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved.November 2018 9 DEMO Creating a Fabric
  10. 10. Copyright © 2005 - 2018 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved.November 2018 10 Fabrics & Systems A Service Fabric may host multiple Systems: a System is a distributed composite Application. Each System is composed of one or more System Parts. Each System Part is runtime isolated: ➡ If a Container Image ➤ install in its own Docker Container. ➡If an OSGi assembly ➤ install in its own framework. A System Part may be a lightweight Microservice written in any language (Java / OSGi, Python, Go, … ), or an Application (e.g. PostgreSQL, Kafka, Spark).
  11. 11. Copyright © 2005 - 2018 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved.November 2018 11 Dependencies, Configuration & Interactions Dependencies: A System’s internal runtime dependencies are automatically managed: 1. `C` having no dependences will immediately start. 2. `B` is dependent upon C, so waits for service `C` 3. `A` is dependent upon B, so waits for service `B` Configuration: System Part Configuration may be via: ➡ Convention (e.g. ENV variables) ➡ Custom Configuration (e.g. API, or file) ➡ ConfigAdmin (if OSGi) Interaction: Is the concern of each System - not dictated by the platform. The Service Fabric is NOT ‘opinionated’: REST / Microservices , RPC µServices, Event / Messaging - are all OK!
  12. 12. Copyright © 2005 - 2018 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved.November 2018 12 Isolation & System / Service Scopes Each System automatically shields its internal structural `wiring` from external Parties. This prevents: ➡ Accidental cross wiring between Systems. ➡ Access by external parties (including Internet). A System can optionally choose to increase the scope of visibility for a specified Service, e.g. making a Service visible off Fabric - or `Public` - only then is DNS required.
  13. 13. Copyright © 2005 - 2018 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved.November 2018 13 DEMO
  14. 14. Copyright © 2005 - 2018 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved.November 2018 14 Target State & Consensus The Fabric Ensemble ➡ Fabric wide System Target State & Configuration. ➡ Dynamically formed. ➡ Secure by Default. ➡ Persisted through Fabric restarts. One should NEVER couple independent Applications / Business Services / via a single shared Consensus Service, therefore…
  15. 15. Copyright © 2005 - 2018 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved.November 2018 15 Application Dedicated Ensembles Application Ensembles ➡ Rapidly (in seconds) and simply - Create, Manage & Repair / Re- Form dedicated Ensembles. ➡ Runtime secure. ➡ Ability to locate at most appropriate ‘frame-of-reference’ for each Application within a Fabric runtime. ➡ Preserved through Fabric restarts.
  16. 16. Copyright © 2005 - 2018 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved.November 2018 16 DEMO
  17. 17. Copyright © 2005 - 2018 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved.November 2018 17 ➡ OSGi R7 based Microservices ➡ REST Microservices composed of OSGi µServices! ➡ see https://enroute.osgi.org Truly Modular Applications
  18. 18. Copyright © 2005 - 2018 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved.November 2018 18 DEMO
  19. 19. Copyright © 2005 - 2018 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved.November 2018 19 DEMO IoT `Edge Cloud` https://projects.eclipse.org/proposals/eclipse-sensinact
  20. 20. Copyright © 2005 - 2018 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved.November 2018 20 Holonic - A Self-Similar Hierarchy A Fabric a group of Fibres A Federation a group of Fabrics A Fibre
  21. 21. Copyright © 2005 - 2018 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved.November 2018 21 Resource & Service Discovery Gossip Group T=0 Initial Peers Gossip Group T=n ➡ A clean room Java / OSGi implementation of an Epidemic Gossip based discovery mechanism. Secure by default / Fast Convergence. ➡ Fibres (nodes) are initially configured with a set of known Initial Peers. ➡ Convergence is achieved when all Fibres have discovered all other Fibres in Gossip Cluster. ➡ Fibres in the same Service Fabric may participate in multiple Gossip Clusters.
  22. 22. Copyright © 2005 - 2018 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved.November 2018 22 Fabric Federations & Service Bridges A secure Gossip cluster may be formed from a small number of Fibres selected from many different Service Fabrics ➡ Fabrics may create Application specific Gossip Clusters over which Services can be exposed / shared. ➡ Environments remain isolated from the `Internet` - i.e. no dependency on / requirement for DNS & HTTP / REST.
  23. 23. Copyright © 2005 - 2018 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved.November 2018 23 DEMO
  24. 24. Copyright © 2005 - 2018 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved.November 2018 24 Pulling the pieces together …
  25. 25. Copyright © 2005 - 2018 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved.November 2018 25 embedded devicecustom protocol District 1 OSGi / Custom Bridge Deployment / Update Manager (new behaviours) OSGi Light Monitoring OSGi Light Controller District 2 District 3 Environment Monitoring Modular Federated Smart Cities City Wide Monitoring & Reporting Smart City - Light Management
  26. 26. Copyright © 2005 - 2018 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved.November 2018 Ops Centre Facility IV Manufacturing Facility II Manufacturing Facility III Third Party Cloud IaaS Manufacturing Facility I An Modular Industry 4.0 `Fog` Environment 26 Modular Federated Manufacturing Autonomous Edge Multi-Agent Cyber Physical Systems 3rd Party or on-Premises Clouds
  27. 27. Copyright © 2005 - 2018 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved.November 2018 27 BRAIN-IoT Convergence of AI and the Adaptive Modular Runtime http://www.brain-iot.eu
  28. 28. Copyright © 2005 - 2018 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved.November 2018 Brian-IoT: Mission Critical City Infrastructure 28 ➡ Operational Simplicity, Security and Robustness paramount. ➡ Real Time Sensing & Data Enrichment at IoT Edge. ➡ Adaptive AI anomaly Detection. ➡ Reactive Device Actuation. ➡ Usage Prediction Services & consumption of 3rd Party Weather Services. Water Utility Infrastructure: location A Coruña, Spain
  29. 29. Copyright © 2005 - 2018 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved.November 2018 Brain-IoT: Adaptive `Smart Factory` environments. 29 ➡ Dynamic Discovery: Robots dynamically discover new IoT devices (Lifts, Doors) ➡ Dynamic Adaption: Robots load appropriate `Smart Behaviours` - enabling adaptive Thing to Thing interactions. ➡ Verifiable & Assured distributed Behaviours: Distributed Orchestration & State Machines, dynamically installed AI & ML. ➡ Local, Autonomous & Self-Protecting: Self-contained modular, evolvable on-premise Cloud.
  30. 30. Copyright © 2005 - 2018 Paremus Ltd. May not be reproduced by any means without express permission. All rights reserved.November 2018 www.paremus.com The Service Fabric, IoT & Fog www.paremus.com @Paremus info@paremus.com https://www.youtube.com/watch?v=H_E1s2UUlX4&feature=youtu.be

×