Better Deployments with Sub Environments Using Spring Cloud and Netflix Ribbon
3 likes792 views
The document discusses the challenges of cloud-native development and continuous deployment, highlighting issues such as testing, configuration, and the need for reliable environments. It introduces Netflix Ribbon and Zuul as solutions for inter-process communication and API gateway functionalities, emphasizing their roles in dynamic routing, load balancing, and monitoring. Additionally, it provides insights into automating transitions between sub-environments and the importance of error handling in service communication.
Better Deployments with Sub Environments Using Spring Cloud and Netflix Ribbon
- 1. 1 © 2018 Pivotal Better Deployments with sub environments using Spring Cloud & Netflix Ribbon Roi Ezra, Infrastructure & Cloud Native Platform team lead, Intel @RoiEzra Liel Chayoun, Infrastructure & Cloud Native Platform developer, Intel @ChayounLiel
- 2. 2 Agenda § Cloud Native & CD Challenges § The Immune System § API Gateway, Netflix Ribbon & Zuul High Level § Demo § Q&A
- 3. 3 Cloud Native & CD Challenges § Microservices • Dynamic Environment • Complex Architecture • Hard to Test
- 4. 4 Cloud Native & CD Challenges § Frequent releases to production • Move fast without breaking things • Prevention > Detection ? Not possible L • Prevention @ Stage N === Detection @ Stage N-1
- 5. 5 Cloud Native & CD Challenges § Testing • How do we fill databases with real data? • What and when to mock? § Configuration • Firewalls, Application Configuration, Connection Strings… § Work loads § Users “There is no place like production”
- 6. 6 The Immune System “The immune system is a host defense system comprising many biological structures and processes within an organism that protects against disease. To function properly, an immune system must detect a wide variety of agents, known as pathogens, from viruses to parasitic worms, and distinguish them from the organism's own healthy tissue. In many species, the immune system can be classified into subsystems, such as the innate immune system versus the adaptive immune system, or humoral immunity versus cell-mediated immunity Wikipedia “
- 7. 7 The Immune System § Tests (Unit, Integration, Contract, Smoke, E2E, Rollback …) § Monitoring & Alerts (Telemetry, Logs) § Semantic Monitoring (Application Level Monitoring) § Chaos Engineering § Several Environments & Sub Environments
- 8. 8 Environments Test Staging / Integration Production… ? ?
- 9. 9 Sub Environments Unstable QA Internal Customers Main Prevention @ Stage N === Detection @ Stage N-1 Production
- 10. 10 Sub Environments § All sub environments must have traffic all the time § Consistency and Standardization § Alerts severity should be different between environments
- 11. 11 When we move to the next sub environment § Should be automatic and based on several inputs: • Application Level Monitoring Results • Telemetry Data • Log Analysis • Pre Defined Schedule
- 12. 12 Enough with challenges Lets see some solutions J
- 13. 13 Netflix Ribbon Ribbon is a Inter Process Communication (remote procedure calls) library with built in software load balancers. The primary usage model involves REST calls with various serialization scheme support.
- 14. 14 Ribbon Components § ServerList - can be static or dynamic § ServerListFilter - filters the servers returned from dynamic server list § Ping - running in background to ensure liveness of servers § Rule - a logic component to determine which server to return from a list
- 15. 15 Ribbon & Spring Cloud § Spring Auto Configuration will automatically detect your dependencies and will configure Ribbon for you § Each load balancer: • Part of an ensemble of components that work together to contact a remote server on demand • Has unique name • Has it own ApplicationContext => Can have custom behavior § Can be used by @LoadBalanced RestTemplate or Feign
- 16. 16 Ribbon & Spring Cloud – Code Example
- 17. 17 API Gateway Pattern – High Level Architecture Clients APIGateway Service Registry Edge Services Backend Services
- 18. 18 API Gateway Pattern § Dynamic Routing § Encryption, Security § Load Balancing § Different Clients § Service Protection (e.g.: Rate Limit) § Smart Client for services (e.g.: Retry) § Enables different deployment strategies
- 19. 19 Zuul – Netflix API Gateway Zuul is a gateway service that provides dynamic routing, monitoring, resiliency, security, and more
- 20. 20 Netflix Zuul § Was used by Netflix at production scale § Replaced by Zuul 2 in 2016 (was open sourced this year) § Used by Spring Cloud Edgware release train § Spring Cloud Finchley uses Spring Cloud Gateway project
- 21. 21 Netflix Zuul – Request Lifecycle HTTP Request “pre” filters “routing” filters “post” filters Server Request Response “error” filters
- 22. 22 Netflix Zuul & Spring Cloud § Spring Cloud has created an embedded Zuul proxy (@EnableZuulProxy) § By convention, a service with the ID "users", will receive requests from the proxy located at /users § The proxy uses Ribbon to locate an instance to forward to via discovery § RibbonRoutingFilter is in charge to use Ribbon, Hystrix and pluggable HTTP clients to send requests
- 23. 23 Some Specific Requirements § Not to expose all services from service discovery to all clients • Only “Edge” services § Not all services runs in all data centers where the gateway runs • Cross zone load balancing with latency consideration § Direct traffic to sub environment based on: • URL, HTTP Header, User / Group § Weight based load balancing
- 24. 24 Lets see some code API Gateway Edge Edge Backend Backend A B
- 25. 25 Lets see some code API Gateway Edge Edge Backend Backend A B X-tag=A
- 26. 26 Lets see some code API Gateway Edge Edge Backend Backend A B X-tag=A
- 27. 27 Lets see some code API Gateway Edge Edge Backend Backend A B X-tag=A
- 28. 28 Lets see some code API Gateway Edge Edge Backend Backend A B X-tag=B
- 29. 29 Lets see some code API Gateway Edge Edge Backend Backend A B X-tag=B
- 30. 30 Lets see some code API Gateway Edge Edge Backend Backend A B X-tag=B
- 31. 31 Problem Solved? Not really L Edge Backend Edge Backend A B X-tag=A Gateway Tag Based Rule
- 32. 32 Problem Solved? Not really L Edge Backend Edge Backend A B X-tag=A X-tag=A Gateway Tag Based Rule
- 33. 33 Problem Solved? Not really L Edge Backend Edge Backend A B X-tag=A ? Gateway Tag Based Rule X-tag=A
- 34. 34 Client Side Load Balancing Instance 1 Instance 2 Instance 3 Service Discovery / Configuration Service Load balancer
- 35. 35 Code Again J
- 36. 36 © 2018 Pivotal Q&A § Code Again J
- 37. 37 Learn More. Stay Connected. § Watch our talk @ the last SP1 Platform about our Cloud Native Journey @ Intel § Demo Code @ GitHub Twitter: twitter.com/springcentral YouTube: spring.io/video LinkedIn: spring.io/linkedin Google Plus: spring.io/gplus https://www.youtube.com/watch?v=D_kt9pMQ4Sw https://github.com/ezraroi/BetterDeploymentsDemo