NASA-IMPACT / NASA-IMPACT/veda-odd
Implement plan, (presumably this will include edge caching and cache invalidation)
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 5
- Forks
- 0
- Avg merge
- 4d 19h
- Merged PRs (30d)
- 3
Description
The ADR should include:
- define what the benchmarks are and how will we assess performance before and after
- ADR should include a plan to have similar "stop when full" logic that titiler-pgstac has, CMR should have bounding box information so we may be able to do the fill logic based on that.
- ADR may include edge caching and cache invalidation plan
- ADR may include provisioned concurrency options in lambda
- Include a long-term option to use a container which will likely work better than a lambda, when making the same requests for tiles, we can take advantage of gdal cache. Lambda has cold start issues.
- Add deployment plan in coordination with VEDA data services team
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by drafting the ADR around the requested benchmark definition and before/after performance assessment. Cover the proposed stop-when-full logic using titiler-pgstac and CMR bounding-box data, edge caching and invalidation, Lambda provisioned concurrency, and a container/GDAL-cache option. Document the deployment plan and coordination with the VEDA data services team; completion means these options and tradeoffs are recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, documentation, performance
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100