Spring Cloud + Netflix OSS

1. MicroServiceArchitecture
Spring Cloud + Netflix OSS
Md. Hasan Basri (Angel)
Full Stack Java SE/EE Engineer | Life Long Learner
www.linkedin.com/in/pothiq/
pothiq@gmail.com

2. Monolithic Vs MicroService

3. What is it?
• Loosely coupled service oriented architecture with
bounded contexts. ~ Adrian Cockcroft
• Small autonomous services that work together.
~ Sam Newman
• MicroServies are a new way to build applications by
breaking them up into small, independent services.
• No specific language
• No heavy middleware
• Mostly open-source

4. Benefits

5. Drawbacks
• Additional complexity of distributed systems.
• Significant operational complexity, need high-
level of automation.
• Rollout plan to coordinate deployments.
• Slower ROI to begin with.

6. When and Why?
• Scale application components independently
• Roll out features or experiments more freely
• Faster iteration
• Greater Resiliency
• Better Availability
• Be aware of challenges
1. API Interface
2. Communication
3. Latency
4. Tooling

7. Where?

8. Portfolio

9. SOA v/s MicroService

10. Technology Stack

11. Basic Scenario

12. High Level View

13. Enterprise Microservice Scenario

14. Tools

15. NETFLIX OSS

16. Netflix uses Zuul for the following:
• Authentication
• Insights
• Stress Testing
• Canary Testing
• Dynamic Routing
• Service Migration
• Load Shedding
• Security
• Static Response handling
• Active/Active traffic management

17. Gateway

18. Eureka Service Discovery
• Eureka is a dedicated Service Discovery solution
• Eureka is simple and robust
• Eureka is Highly Available
• Eureka does Client Side Caching
• Eureka is open source and maintained by Netflix
• Spring Cloud invests supports and promotes
Eureka through Spring Cloud Netflix

19. Zuul, Ribbon & Eureka

20. Ribbon Load Balancer
• Load balancing
• Fault tolerance
• Multiple protocols (HTTP, TCP, UDP) support in
an asynchronous and reactive model
• Caching and batching

21. Hystrix is designed to do the following:
1. Give protection from and control over latency and failure from
dependencies accessed (typically over the network)
via third-party client libraries.
2. Stop cascading failures in a complex distributed system.
3. Fail fast and rapidly recover.
4. Fallback and gracefully degrade when possible.
5. Enable near real-time monitoring, alerting, and operational control.

22. Hystrix (Circuit Breaker)