fast-gateway
Advanced tools
A super fast, framework agnostic Node.js API Gateway for the masses ❤️
Since v2.3.0, AWS Lambda proxying integration is supported via
http-lambda-proxy🔥
npm i fast-gateway
Next we describe two examples proxying HTTP and Lambda downstream services.
For simplicity of reading, both examples are separated, however a single gateway configuration supports all routes configurations.
const gateway = require('fast-gateway')
const server = gateway({
routes: [{
prefix: '/service',
target: 'http://127.0.0.1:3000'
}]
})
server.start(8080)
const service = require('restana')()
service.get('/get', (req, res) => res.send('Hello World!'))
service.start(3000)
npm i http-lambda-proxy
const gateway = require('fast-gateway')
const server = gateway({
routes: [{
proxyType: 'lambda',
prefix: '/service',
target: 'my-lambda-serverless-api',
lambdaProxy: {
region: 'eu-central-1'
}
}]
})
server.start(8080)
You might also want to read: Setting AWS Credentials in Node.js
const serverless = require('serverless-http')
const json = require('serverless-json-parser')
const query = require('connect-query')
const service = require('restana')()
service.use(query())
service.use(json())
// routes
service.get('/get', (req, res) => {
res.send({ msg: 'Go Serverless!' })
})
service.post('/post', (req, res) => {
res.send(req.body)
})
// export handler
module.exports.handler = serverless(service)
{
// Optional server instance. Any HTTP framework that supports the following signature is compatible:
// - server[HTTP_METHOD](pattern, [middleware1, middleware2,], handler)
//
// Known compatible frameworks: Restana, Express.js
// If omitted, restana is used as default HTTP framework
server,
// Optional restana library configuration (https://www.npmjs.com/package/restana#configuration)
// Please note that if "server" is provided, this settings are ignored.
restana: {},
// Optional global middlewares in the format: (req, res, next) => next()
// Default value: []
middlewares: [],
// Optional global value for routes "pathRegex". Default value: '/*'
pathRegex: '/*',
// Optional global requests timeout value (given in milliseconds). Default value: '0' (DISABLED)
// Ignored if proxyType = 'lambda'
timeout: 0,
// Optional "target" value that overrides the routes "target" config value. Feature intended for testing purposes.
targetOverride: "https://yourdev.api-gateway.com",
// HTTP proxy
routes: [{
// Optional proxy type definition. Supported values: http, lambda
// Default value: http
proxyType: 'http'
// Optional `fast-proxy` library configuration (https://www.npmjs.com/package/fast-proxy#options)
// base parameter defined as the route target. Default value: {}
// This settings apply only when proxyType = 'http'
fastProxy: {},
// Optional `http-lambda-proxy` library configuration (https://www.npmjs.com/package/http-lambda-proxy#options)
// The 'target' parameter is extracted from route.target, default region = 'eu-central-1'
// This settings apply only when proxyType = 'lambda'
lambdaProxy: {
region: 'eu-central-1'
},
// Optional proxy handler function. Default value: (req, res, url, proxy, proxyOpts) => proxy(req, res, url, proxyOpts)
proxyHandler: () => {},
// Optional flag to indicate if target uses the HTTP2 protocol. Default value: false
// This setting apply only when proxyType = 'http'
http2: false,
// Optional path matching regex. Default value: '/*'
// In order to disable the 'pathRegex' at all, you can use an empty string: ''
pathRegex: '/*',
// Optional service requests timeout value (given in milliseconds). Default value: '0' (DISABLED)
// This setting apply only when proxyType = 'http'
timeout: 0,
// route prefix
prefix: '/public',
// Optional documentation configuration (unrestricted schema)
docs: {
name: 'Public Service',
endpoint: '/api-docs',
type: 'swagger'
},
// Optional "prefix rewrite" before request is forwarded. Default value: ''
prefixRewrite: '',
// Remote HTTP server URL to forward the request.
// If proxyType = 'lambda', the value is the name of the Lambda function, version, or alias.
target: 'http://localhost:3000',
// Optional HTTP methods to limit the requests proxy to certain verbs only
// Supported HTTP methods: ['GET', 'DELETE', 'PATCH', 'POST', 'PUT', 'HEAD', 'OPTIONS', 'TRACE']
methods: ['GET', 'POST', ...],
// Optional route level middlewares. Default value: []
middlewares: [],
// Optional proxy lifecycle hooks. Default value: {}
hooks: {
async onRequest (req, res) {
// // we can optionally reply from here if required
// res.end('Hello World!')
//
// // we can optionally update the request query params from here if required
// req.query.category = 'js'
//
// return true // truthy value returned will abort the request forwarding
},
onResponse (req, res, stream) {
// do some post-processing here
// ...
}
// if proxyType= 'http', other options allowed https://www.npmjs.com/package/fast-proxy#opts
}
}]
}
For developers reference, default hooks implementation are located in lib/default-hooks.js file.
Since version 1.3.5 the gateway exposes minimal documentation about registered services at: GET /services.json
Example output:
[
{
"prefix":"/public",
"docs":{
"name":"Public Service",
"endpoint":"/swagger.json",
"type":"swagger"
}
},
{
"prefix":"/admin"
}
]
NOTE: Please see
docsconfiguration entry explained above.
We can restrict requests timeouts globally or at service level using the timeout configuration.
You can also define endpoints specific timeout using the property timeout of the request object, normally inside a middleware:
req.timeout = 500 // define a 500ms timeout on a custom request.
NOTE: You might want to also check https://www.npmjs.com/package/middleware-if-unless
By using the proxyHandler hook, developers can optionally intercept and modify the default gateway routing behavior right before the origin request is proxied to the remote service. Therefore, connecting advanced monitoring mechanisms like Circuit Breakers is rather simple.
Please see the demos/circuitbreaker.js example for more details using the opossum library.
Rate limiting, as well many other gateway level features can be easily implemented using fast-gateway:
const rateLimit = require('express-rate-limit')
const requestIp = require('request-ip')
gateway({
middlewares: [
// first acquire request IP
(req, res, next) => {
req.ip = requestIp.getClientIp(req)
return next()
},
// second enable rate limiter
rateLimit({
windowMs: 1 * 60 * 1000, // 1 minutes
max: 60, // limit each IP to 60 requests per windowMs
handler: (req, res) => res.send('Too many requests, please try again later.', 429)
})
],
// your downstream services
routes: [{
prefix: '/public',
target: 'http://localhost:3000'
}, {
// ...
}]
})
In this example we have used the express-rate-limit module.
Caching support is provided by the http-cache-middleware module. https://www.npmjs.com/package/http-cache-middleware
Because
cachingis the last mile for low latency distributed systems!
Enabling proper caching strategies at gateway level will drastically reduce the latency of your system,
as it reduces network round-trips and remote services processing.
We are talking here about improvements in response times from X ms to ~2ms, as an example.
We use the
http-cache-middlewaremodule to support gateway level caching. Read more about it: https://github.com/jkyberneees/http-cache-middleware
// cache middleware
const cache = require('http-cache-middleware')()
// enable http cache middleware
const gateway = require('fast-gateway')
const server = gateway({
middlewares: [cache],
routes: [...]
})
Memory storage is recommended if there is only one gateway instance and you are not afraid of losing cache data.
// redis setup
const CacheManager = require('cache-manager')
const redisStore = require('cache-manager-ioredis')
const redisCache = CacheManager.caching({
store: redisStore,
db: 0,
host: 'localhost',
port: 6379,
ttl: 30
})
// cache middleware
const cache = require('http-cache-middleware')({
stores: [redisCache]
})
// enable http cache middleware
const gateway = require('fast-gateway')
const server = gateway({
middlewares: [cache],
routes: [...]
})
Required if there are more than one gateway instances
https://github.com/jkyberneees/http-cache-middleware#enabling-cache-for-service-endpoints
https://github.com/jkyberneees/http-cache-middleware#invalidating-caches
Cache keys are generated using: req.method + req.url, however, for indexing/segmenting requirements it makes sense to allow cache keys extensions.
Unfortunately, this feature can't be implemented at remote service level, because the gateway needs to know the entire lookup key when a request
reaches the gateway.
For doing this, we simply recommend using middlewares on the service configuration:
routes: [{
prefix: '/users',
target: 'http://localhost:3000',
middlewares: [(req, res, next) => {
req.cacheAppendKey = (req) => req.user.id // here cache key will be: req.method + req.url + req.user.id
return next()
}]
}]
In this example we also distinguish cache entries by
user.id, very common case!
You can also disable cache checks for certain requests programmatically:
routes: [{
prefix: '/users',
target: 'http://localhost:3000',
middlewares: [(req, res, next) => {
req.cacheDisabled = true
return next()
}]
}]
Benchmark scripts can be found in benchmark folder.
Laptop: MacBook Pro 2016, 2,7 GHz Intel Core i7, 16 GB 2133 MHz LPDDR3
wrk -t8 -c50 -d20s http://127.0.0.1:8080/service/get
You can support the maintenance of this project:
nano_3zm9steh8mb374f8be3rbytqhgzzarczhwtxhihkqt83a4m46oa3xidfiaucrarQgNuiqF9gFLLwd5fdku4jYa9EXpiyCpTJ5Bbf9v4kpptnRsePXYDvnYcYrS5Tyxusbc1qcrr58venyh54ztvkqym39p9rhnxg4308t0802f0xD73c8E63a83eBD8Df3fB3d0090f1fe7a1eEB980BFAQs
A Node.js API Gateway for the masses!
The npm package fast-gateway receives a total of 704 weekly downloads. As such, fast-gateway popularity was classified as not popular.
We found that fast-gateway demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
An advanced npm supply chain attack is leveraging Ethereum smart contracts for decentralized, persistent malware control, evading traditional defenses.
Security News
Research
Attackers are impersonating Sindre Sorhus on npm with a fake 'chalk-node' package containing a malicious backdoor to compromise developers' projects.
Security News
The npm package for the LottieFiles Player web component was hit with a supply chain attack after a software engineer's npmjs credentials were compromised.