openmobilityfoundation / openmobilityfoundation/mobility-data-specification
Expected QPS, latency, and data retention
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 746
- Forks
- 252
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 2
Description
Providing frequent and quick access to an ever growing set of data will obviously put pressure on provider's infrastructure, especially for new or smaller providers which may not have as sophisticated technology stacks. I think that we should establish explicit limits and expectations around QPS, latency, and data retention.
QPS/Load
- What kind of QPS should providers expect on these APIs?
- As a provider, I expect we will want to enforce rate limits, what are acceptable limits?
Latency
- What is an acceptable latency?
- Should we consider asynchronous implementations for providers that cannot meet latency expectations easily?
Data Retention
- What is the expected data retention? Indefinite?
Contributor guide
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
No files, tests, or implementation entry points are identified. Start by resolving the proposed QPS and rate-limit expectations, acceptable latency or asynchronous behavior, and data-retention policy; done would be a documented decision that can be applied consistently to the APIs.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100