Variations

Explore various technology alternatives to the Netflix stack for synchronous microservices, including Zuul2, Spring Cloud Gateway, Consul, Kubernetes, and HTTP proxies like Envoy. Learn their differences in service discovery, routing, load balancing, and resilience, and understand how frontend integration and asynchronous communication can complement these approaches.

We'll cover the following...

- Zuul2
- resilience4j
- Consul
- Kubernetes
- HTTP proxy
- Atom
- Frontend integration

Netflix is only one technological option for implementing synchronous microservices.

There are various alternatives to the technologies of the Netflix stack.

Zuul2 #

The Zuul project is not maintained very well anymore. An alternative might be Zuul2. It is based on asynchronous I/O so it consumes less resources and is more stable. However, Spring Cloud won’t support Zuul2. Another alternative might be Spring Cloud Gateway. The approach with Apache for routing shown in chapter 11 and Kubernetes in chapter 13 is probably even better.

1.Preface

2.Self-contained Systems

3.Concept: Frontend Integration

4.Recipe: Links and Client-side Integration

5.Recipe: Server-side Integration using Edge Side Includes (ESI)

6.Concept: Asynchronous Microservices

7.Recipe: Messaging and Kafka

8.Recipe: Asynchronous Communication with Atom and REST

9.Concept: Synchronous Microservices

Project

10.Recipe: REST with the Netflix Stack

11.Recipe: REST with Consul and Apache httpd

12.Concept: Microservices Platforms

13.Recipe: Docker Containers with Kubernetes

14.Recipe: PaaS with Cloud Foundry

Project

15.Appendix

Variations

Zuul2 #

resilience4j #