NATS vs HTTP
5 likes3,238 views
The document compares traditional HTTP architecture and NATS microservice architecture, highlighting the drawbacks of HTTP in microservice environments, such as load balancing and service discovery issues. NATS is presented as a lightweight, flexible, and high-performance alternative that aligns well with modern microservice patterns. It includes benchmark setup and results, discussing various NATS strategies and considerations for implementing inter-service communication.
Related topics:1 of 9
Downloaded 30 times
NATS vs HTTP
- 1. NATS vs HTTP Inter service communication
- 2. Agenda ● Traditional HTTP Architecture ● NATS Microservice Architecture ● Benchmark setup ● Benchmark results ● Migration Considerations
- 3. Traditional HTTP Architecture ● Drawbacks: ○ Load Balancing ○ Service Discovery ○ Each service must have a dedicated WebServer ● Doesn't fit the microservice model
- 4. NATS Microservice Architecture ● Fits the new Microservice patterns ● NATS is ○ Lightweight ○ Flexible ○ Highly Performant ● It becomes easier to create microservices ○ Load Balancing ○ Service Discovery
- 5. Benchmark setup ● Running with Docker ● One Client ● One Proxy ● One Service ● Source code ○ https://github.com/diogogmt/nats-rest-benchmark
- 6. Benchmark Results ● Each request is executed serially ● Client times how long it takes to execute all requests
- 7. Benchmark Results ● Client executes requests concurrently with a factor of 20%
- 8. Considerations ● Different NATS strategies ○ Pub/Sub ○ Request/Reply ○ Queuing ● Keep in mind ○ Concurrency ○ Session Management ○ Metadata ○ Message status ○ NATS-Proxy framework ■ Author: Radomír Sohlich ■ https://github.com/sohlich/nats-proxy