Variations

In this lesson, we'll discuss some variations to the approaches we've already looked at.

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.

Get hands-on with 1400+ tech skills courses.

Preface

Self-contained Systems

Concept: Frontend Integration

Recipe: Links and Client-side Integration

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

Concept: Asynchronous Microservices

Recipe: Messaging and Kafka

Recipe: Asynchronous Communication with Atom and REST

Concept: Synchronous Microservices

Recipe: REST with the Netflix Stack

Recipe: REST with Consul and Apache httpd

Concept: Microservices Platforms

Recipe: Docker Containers with Kubernetes

Recipe: PaaS with Cloud Foundry

Appendix

Variations

Zuul2 #