It’s true, we’ve slowed down on Express Gateway. Why? We’ve been pretty busy supporting developers deploying instances of Express Gateway on production environments. We are thrilled at this opportunity, but like any other open source project we’ve found a few edge cases. So, where to go from here?

In case you missed the important news - we released an update to Express Gateway with support for JSON Web Tokens (JWT). Now, we’d like to take a moment and go into more depth on how you can get started with JWT and Express Gateway.

There are a lot of resources out there when it comes to exploring the ins-n-outs of environment variables. Recently, we added support for environment variables in Express Gateway as a response to request we received from developers who are using Express Gateway in production right now. So, we’d like to take a moment and go into more depth on how you can get started with Environment Variables and Express Gateway.

Express Gateway and Amazon API Gateway are two different products for configuring middleware servers that provide services like rate limiting, authentication, and proxying. As a developer, I want to share the major trade-offs between using Amazon API Gateway and Express Gateway across several important dimensions.

We love open source and we especially love feedback from our community. It’s not even February yet, and we’ve been busy jamming out the features developers, like you, have been requesting including Node.js 9, JSON Schemas and more. If you’ve tried out Express Gateway, you’re in the right place because this next feature in Express Gateway 1.7.0 is small, but mighty. Join us in exploring environment variables in both configuration stacks.