A sail in the cloud
3 likes1,682 views
The document discusses microservice architecture, which involves developing applications as a suite of small, independently deployable services. It highlights key principles such as canary releases and circuit breakers, along with tools like Istio and Envoy for monitoring and managing service communication. The document also includes references to demos and resources for further exploration of these concepts.
A sail in the cloud
- 1. 1 Sail in the Cloud @kamesh_sampath ksampath@redhat.com
- 3. The microservice architectural style is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API. These services are built around business capabilities and independently deployable by fully automated deployment machinery. There is a bare minimum of centralized management of these services, which may be written in different programming languages and use different data storage technologies. Martin Fowler What is a microservice ?
- 6. Istio Service Mesh Envoy istio-ingress Envoy App A Envoy App B Envoy App C istio-pilot istio-mixer istio-auth HTTP Req/Resp Kubernetes Pods Istio Components Config to Envoy Access Control and Telemetry
- 7. Istio Components ● Control Plane ○ Istio-Pilot ■ Traffic Management ○ Istio-Mixer ■ Access Control ○ Istio-Auth ■ TLS and Certificates ● Data Plane ○ Envoy proxy deployed as “side-cars” with applications
- 8. Sidecar
- 9. SideCars git-sync ngnix ● Two or more containers deployed to same pod ● Share ○ same namespace ○ same Pod IP ○ Shared lifecycle ● Used to enhance the containers Composite Container Application Source: http://blog.kubernetes.io/2015/06/the-distributed-system-toolkit-patterns.html Pod web-sources(Volume)
- 10. Demo
- 12. Istio - Distributed Tracing ● Zero code change ● Propagate set of headers ○ x-request-id ○ x-b3-traceid ○ x-b3-spanid ○ x-b3-parentspanid ○ x-b3-sampled ○ x-b3-flags ○ x-ot-span-context ● Integrated with Zipkin
- 13. Demo
- 14. Canary Release
- 15. Canary release is a technique to reduce the risk of introducing a new software version in production by slowly rolling out the change to a small subset of users before rolling it out to the entire infrastructure and making it available to everybody. Source: https://martinfowler.com/bliki/CanaryRelease.html Microservice Architecture - Principles Canary Release
- 17. Canary Deployment DEVELOPMENT QA STAGING PRODUCTION INGRESS USERS SCM
- 18. Canary Deployment DEVELOPMENT QA STAGING PRODUCTION INGRESS USERS SCM
- 19. Canary Deployment DEVELOPMENT QA STAGING PRODUCTION INGRESS USERS SCM
- 20. Canary Deployment DEVELOPMENT QA STAGING PRODUCTION INGRESS USERS SCM
- 21. Canary Deployment DEVELOPMENT QA STAGING PRODUCTION INGRESS USERS SCM
- 22. Canary Deployment DEVELOPMENT QA STAGING PRODUCTION INGRESS USERS SCM
- 23. Canary Deployment DEVELOPMENT QA STAGING PRODUCTION INGRESS USERS SCM
- 24. Canary Deployment DEVELOPMENT QA STAGING PRODUCTION INGRESS USERS SCM
- 25. Canary Deployment DEVELOPMENT QA STAGING PRODUCTION INGRESS USERS SCM
- 26. Canary Deployment DEVELOPMENT QA STAGING PRODUCTION INGRESS USERS SCM
- 27. Demo
- 28. Circuit Breakers
- 29. The basic idea behind the circuit breaker is very simple. You wrap a protected function call in a circuit breaker object, which monitors for failures. Once the failures reach a certain threshold, the circuit breaker trips, and all further calls to the circuit breaker return with an error, without the protected call being made at all Source: https://martinfowler.com/bliki/CircuitBreaker.html Microservice Architecture - Principles Circuit Breaker
- 30. Demo
- 31. Summary ▪ Minikube ▪ Docker Maven Plugin ▪ Service Mesh https://istio.io ▪ Demo Repo - https://goo.gl/pRKKqL @kamesh_sampath developers.redhat.com