Background information
After a few tests with tegola vector-tile service using Swift as cache storage, we realised that organic cache could be a viable option. This task is to evaluate and decide if we will enforce tile seed during OSM sync or if we will only invalidate expired tiles and let tegola seed the cache organically.
What
Tile seed during OSM sync is the status quo with Tilerator. With Tegola we have the option to do organic cache, which decreases the complexity of the architecture but still needs to be benchmarked.
How
Benchmark organic cache vs tile seed during OSM sync
Open questions
...
Acceptance criteria
- Documentation is updated
- A decision statement is submitted and a follow-up task to do the remaining work is created