We’re pleased to announce we’ve released Express Gateway 1.3.0. This version fixes bugs and we’re excited to share brand new features for developers to test drive!
-
Announcing Express Gateway v1.3.0
-
Intro to the Rate Limiting Policy
Express Gateway has a lot of powerful features beyond just auth. Another important feature is rate limiting, which throttles requests to one or more endpoints. Express Gateway has a lot of tuneable options for configuring throttling: you can throttle requests on a per user, per endpoint, or per pipeline basis. In this article, I’ll walk you through a “Hello, World” example of using Express Gateway’s rate limiting policy, and then show a practical use case of rate limiting based on user API keys.
-
How to Use Scopes to Secure Your API
Express Gateway has built-in support for numerous authentication mechanisms, like OAuth2 and key auth. On top of these authentication mechanisms, Express Gateway supports restricting access to certain endpoints to certain users using the notion of scopes. In this article, I’ll provide a “Hello, World” example of using scopes and then dive into a more realistic example of using scopes to protect access to an external API.
-
Express Gateway and Kubernetes - Part 1
It’s no secret that cloud native applications are designed to maximize resilience through predictable behaviors. Several factors, including API exposure and application design, play key roles in the successful deployment of cloud native applications. For instance, API exposure and providing internal or external access via standardized methods can fundamentally change your growth trajectory. You can create new services, integrations and expose customer insights. As an important area of growth, designing your application also plays a critical role. Are you designing with microservices in mind? Breaking down monolithic applications with containers? For example, cloud native technologies like Docker give you the ability to decompose your once monolithic applications into sustainable microservices. If you’re building the next generation of cloud native applications, where what does that roadmap look like? Let’s break it down.
-
Part 1 - Anatomy of a Plugin
“Give a man a fish, and you feed him for a day. Teach a main to fish, and you feed him for a lifetime.”
This old saying is the premise behind what we were thinking of building next based on community feedback of what we had released initially with Express Gateway.