v1.14.0
Express Gateway v1.14.0 has been released.
This release fixes some bugs reported by users that are continuously using Express more and more and some a new requested feature.
Changed
- The Rate Limiter policy will now use the Redis client to store its counters. This means that, in case you have multiple instance of Express Gateway running, the counters will be shared as long you're using a common Redis instance. In case you're on an in-memory experience, the behaviour will be exactly the same as you were experiencing before. This will hopefully open the doors for a new class of Express Gateway deployments; we can't wait to see this live! 🚀 #858
- The old and outdated Swagger document has been removed from Express Gateway along with the middleware serving the doc from the Admin API. We have in mind to rebuild the docs based on OpenAPI 3.0, but that's going to require some time #847
- We have updated all our dependencies to the last reasonable version #858
Added
- Express Gateway is now adopting the LTS Module policy by CloudNativeJs.io. This will ensure predictability with compatibility with various NodeJS version and also — I'm proud to announce Express Gateway is now a listed module in CloudNativeJS modules. #851
- It is now possible to specifically bind the hostname for the
httpandhttpsservers. This might be particularly useful when using Express Gateway in Docker environments #846
Express Gateway in production? Let us know!
As always, we're open to any feedback and ready to hear your story of putting Express Gateway in production. In case you're interested, please reach us on Gitter, via email or in any way you want.