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.

Microservices on the Edge


Published on

How concepts from cloud native architecture can be used to drive edge computing/fog computing architecture

Published in: Technology
  • Be the first to comment

Microservices on the Edge

  1. 1. Microservices on the Edge James Higginbotham API Architect @launchany
  2. 2. Introduction
  3. 3. A Little Background…
  4. 4. Fog Computing The collaboration of resources from ‘edge nodes’ for the purposes of computation, storage, analysis and management of devices and data
  5. 5. Edge Computing in 2001 +
  6. 6. What’s Different Now?
  7. 7. Cloud Native Architecture Need Solution Servers Cloud Servers are abundant (e.g. EC2) Database Various vendors, can scale up and out (e.g. RDS or self-install) File Storage File and Object storage abundant (e.g. EFS, S3, Ceph) Messaging Message brokers abundant (e.g. SNS/SQS, RabbitMQ) Stack Definition Declarative Infrastructure (e.g. CloudFormation, SaltStack, Terraform, BOSH)
  8. 8. Edge Computing Architecture Need Solution Servers Hardware must be installed ahead of time Database Limited footprint/storage requires careful selection File Storage File storage limited, can cluster block devices Messaging Message brokers abundant, limited by footprint requirements Stack Definition Infrastructure is hardware
  9. 9. Edge computing demonstrates some of the same limitations of the pre-cloud world: No elasticity or flexibility
  10. 10. What if we could bring some elasticity and flexibility of our cloud native architecture to edge computing?
  11. 11. The Proof of Concept
  12. 12. Hardware List • Raspberry Pi 2 • 6-port USB Charger • 1’ micro USB cables • 1’ Cat 5 cables + switch • 3’ thin HDMI cables • HDMI Switcher (optional) • Projector (optional, for initial Pi configuration)
  13. 13. Docker Environment • Hypriot Raspbian distribution • Docker 1.6.0 • OverlayFS • • Docker Images: • hypriot/rpi-redis • hypriot/rpi-ruby • (Also avail: Node, Go, Python, Java, MySQL, …)
  14. 14. Architecture RedisMessage Broker Dashboard WX API Solar Panel API Platform Services Application Services Solar Panel Aggregator WX Collector Solar Panel Collector Microservice Boundary
  15. 15. Demo
  16. 16. Future Considerations  Build trigger logic from events/analysis  Shared platform services – Device-specific integration services (logging/ELK) – Network-specific services (MQTT, Internal DNS)  Service discovery and orchestration – Docker Swarm, Hashicorp Consul/Atlas  Deployment services – Upgrade/rollback using blue-green deployment
  17. 17. Thanks Ya’ll James Higginbotham @launchany
  18. 18. QUESTIONS