We have seen through multiple articles how an API Gateway can help you in the difficult task of providing an uniform API regardless of the underlying set of microservices. However, we haven’t been exploring another set of problems that arise in case you want to go with such architecture.

Express Gateway is cloud native software, meaning that it integrates easily with Kubernetes or any other container orchestration solution.

Let’s explore an interesting use case where you can use Express Gateway with Kubernetes to provide a graceful degradation for clients in case some of its managed services are down.

We’re back with more about how you can use Transport Layer Security (TLS) Client Authentication from the latest 1.8.0 release. We’ll cover how to revoke a client certificate and special use cases if you want to use TLS Authentication for a specific path.

Express Gateway supports various client authentication methods such as key auth,basic auth,jwt. Based on developer community feedback, we’ve included support to Transport Layer Security (TLS) Client Authentication in the latest 1.8.0 release.

So, we can code up some new and interesting scenarios. Let’s dig in!