Static Cache

Last edit: Oct 26, 2022

Static cache means you create a static response, and serve it bypassing the whole server side, including authorization. It is similar to server-side rendering. It is faster because it bypasses the application server completely.

Although it's fast, you can rarely use it. For example, it's great to use this for the home page, to make it very fast for non-authenticated users, but you can't do the same for a dashboard, because the user has to be authenticated.

Use cases

Static cache is a great candidate to use when creating a sitemap that you want to have updated at most once a day.

Many developers use it also for their JSON API that has to respond as fast as possible but the data does not change often and is not dependent of the user requesting the data.


For example, if you were to build a currency exchange rates API, you might want to fetch data from the database at most once a minute, not more often.


  expire: 60 # response will be cached for 60 seconds (or 1 minute)
  "PLN": "{{ 10 | random_string }}",
  "USD": "{{ 10 | random_string }}",
  "CHF": "{{ 10 | random_string }}",
  "AUD": "{{ 10 | random_string }}",
  "JPY": "{{ 10 | random_string }}"


Keep in mind that there are multiple servers behind our load balancers and each of them have separate cache, so you might encounter different results depending on hitting a server with warm cache or cold cache.

Source code and demo

You can find the source code of this example on GitHub, and a demo on our examples page.


We are always happy to help with any questions you may have.

contact us