From 1852d9459b43b062d66e482a528f976f796f1eba Mon Sep 17 00:00:00 2001 From: Aimee Barciauskas Date: Mon, 2 Oct 2023 15:15:38 -0700 Subject: [PATCH] Add future areas --- approaches/tiling/future-areas.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/approaches/tiling/future-areas.md b/approaches/tiling/future-areas.md index 7278dbd..4edf355 100644 --- a/approaches/tiling/future-areas.md +++ b/approaches/tiling/future-areas.md @@ -2,10 +2,12 @@ At this time, we plan to develop the tile server approach in the following areas: -* Implement caching at the application level with zarr metadata caching -* Implement caching at the API level with CloudFront +* Implement caching at the application level with zarr metadata caching. +* Implement caching at the API level with CloudFront. * Make consolidated metadata optional and benchmark the difference between consolidated and non-consolidated metadata. At this time, the following areas of research and development are of interest but unplanned: -* Implement guidance on exactly when +* Exacting guidelines on when to create pyramids. For example, if your dataset is `x` chunk shape/size, and you expect `y` performance, you should or should nnot create `z` levels of pyramid. +* Understand the impact of latency and caching for layers of AWS services. We expect there may be some caching in the S3 service but have not tested or verified this. +* There is latency introduced with the API Gateway and Lambda services. It may be helpful to estimate the latency for these layers and different expected dataset configurations.