{"action":"created","issue":{"url":"https://api.github.com/repos/CityOfLosAngeles/mobility-data-specification/issues/84","repository_url":"https://api.github.com/repos/CityOfLosAngeles/mobility-data-specification","labels_url":"https://api.github.com/repos/CityOfLosAngeles/mobility-data-specification/issues/84/labels{/name}","comments_url":"https://api.github.com/repos/CityOfLosAngeles/mobility-data-specification/issues/84/comments","events_url":"https://api.github.com/repos/CityOfLosAngeles/mobility-data-specification/issues/84/events","html_url":"https://github.com/CityOfLosAngeles/mobility-data-specification/issues/84","id":361805732,"node_id":"MDU6SXNzdWUzNjE4MDU3MzI=","number":84,"title":"Expected QPS, latency, and data retention","user":{"login":"noonhub","id":942363,"node_id":"MDQ6VXNlcjk0MjM2Mw==","avatar_url":"https://avatars0.githubusercontent.com/u/942363?v=4","gravatar_id":"","url":"https://api.github.com/users/noonhub","html_url":"https://github.com/noonhub","followers_url":"https://api.github.com/users/noonhub/followers","following_url":"https://api.github.com/users/noonhub/following{/other_user}","gists_url":"https://api.github.com/users/noonhub/gists{/gist_id}","starred_url":"https://api.github.com/users/noonhub/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/noonhub/subscriptions","organizations_url":"https://api.github.com/users/noonhub/orgs","repos_url":"https://api.github.com/users/noonhub/repos","events_url":"https://api.github.com/users/noonhub/events{/privacy}","received_events_url":"https://api.github.com/users/noonhub/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-09-19T15:32:37Z","updated_at":"2018-10-07T20:56:05Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"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.\r\n\r\nQPS/Load\r\n * What kind of QPS should providers expect on these APIs? \r\n * As a provider, I expect we will want to enforce rate limits, what are acceptable limits?\r\n\r\nLatency\r\n * What is an acceptable latency?\r\n * Should we consider asynchronous implementations for providers that cannot meet latency expectations easily?\r\n\r\nData Retention\r\n * What is the expected data retention? Indefinite?\r\n"},"comment":{"url":"https://api.github.com/repos/CityOfLosAngeles/mobility-data-specification/issues/comments/427686249","html_url":"https://github.com/CityOfLosAngeles/mobility-data-specification/issues/84#issuecomment-427686249","issue_url":"https://api.github.com/repos/CityOfLosAngeles/mobility-data-specification/issues/84","id":427686249,"node_id":"MDEyOklzc3VlQ29tbWVudDQyNzY4NjI0OQ==","user":{"login":"hunterowens","id":1735650,"node_id":"MDQ6VXNlcjE3MzU2NTA=","avatar_url":"https://avatars2.githubusercontent.com/u/1735650?v=4","gravatar_id":"","url":"https://api.github.com/users/hunterowens","html_url":"https://github.com/hunterowens","followers_url":"https://api.github.com/users/hunterowens/followers","following_url":"https://api.github.com/users/hunterowens/following{/other_user}","gists_url":"https://api.github.com/users/hunterowens/gists{/gist_id}","starred_url":"https://api.github.com/users/hunterowens/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hunterowens/subscriptions","organizations_url":"https://api.github.com/users/hunterowens/orgs","repos_url":"https://api.github.com/users/hunterowens/repos","events_url":"https://api.github.com/users/hunterowens/events{/privacy}","received_events_url":"https://api.github.com/users/hunterowens/received_events","type":"User","site_admin":false},"created_at":"2018-10-07T20:56:05Z","updated_at":"2018-10-07T20:56:05Z","author_association":"MEMBER","body":"Ref for #105, we should have an error code for \"data no longer stored\" \r\n\r\nOn one hand, would love to standardize, on the other than, different jurisdictions == different retention schedules. "}}
{"actor":{"display_login":"hunterowens"}}