dacap
Dynamic And Compressing Api Proxy is a service which lets you proxy arbitrary API-Endpoints which are by themself to slow to be used in production environments. All cached Responses are held in memory, so be sure to provide enough.
Requirements
- node >= v8.2.1
- npm >= v5.3.0
Install the service
$# npm install -g dacap
Start the service
$# dacap
The Admin Interface is now available under http://localhost:3000/admin
You can customize multiple values, see [#Advanced Configuration]
Usage
First of all one has to define a Cache where the requests to an API-Endpoint are stored. This is done from within the Admin Interface.
One has to define the URL to the desired API-Endpoint (e.g. http://foo.example.com/
) and a Cache-Name for this API-Endpoint (e.g. foo
). All API-Requests which normally would go to
http://foo.example.com/?query=foo&offset=0&limit=10
now you can request by accessing
http://localhost:3000/ep/foo/?query=foo&offset=0&limit=10
- Be sure to append the Slash after the Cache-Name, otherwise the Endpoint cannot be resolved.
- Everything after the Cache-Name and Slash will be passed to the API-Endpoint.
Advanced Configuration
The service can be configured by environment variables. The following are available:
-
data_dir
: specifies the folder where the cache is stored in intervals. This is only used to make it more easy to restart the service without adding all Endpoints again. After restart the service reads the saved cache-file and keeps it in memory. By default this points to thedata
-folder where the process was invoked. Make sure it can be created if not existing and written if already existing. -
proxy_path
: this is the path where the Endpoints will be accessable after registering. By default this is/ep/
-
proxy_port
: this is the port number where the service is listening. Defaults to3000
-
proxy_url
: this is the absolute url of the service with protocol and port if differing from the defaults (e.g.http://api.example.com:8080
). Set this if you use a different domain name thanlocalhost
to connect to this service. -
cache_ttl
: the time-to-live in seconds of a cached request. after this time the cache will be refreshed. Defaults to600
-
default_check_period
: specifies the interval in seconds the cache is checked for expiry. Defaults to60
-
array_value_size
: unkown configuration. Defaults to40
-
object_value_size
: unkown configuration. Defaults to80
-
autosave_interval
: specifies the interval the cache is stored to harddisk. defaults to60
; -
register_name
: specifies the name of the register where the cache is stored. Defaults toapi-cache
;