Caches

In Koop, the cache stores data from third party providers to reduce redundant requests and speed up response time. Koop’s data caching is by default a local, in-memory object. We strongly recommend using the PostGIS cache for production deployments.

Create a Cache

We encourage you to create your own cache using the Cache specification.

Officially Supported

name version build status
PostGIS npm travis

Experimental

name version build status
ElasticSearch npm travis

Know of any caches that aren’t listed above? Please let us know by submitting an issue!