{"action":"opened","issue":{"url":"https://api.github.com/repos/dulibrarytech/digitaldu-backend/issues/35","repository_url":"https://api.github.com/repos/dulibrarytech/digitaldu-backend","labels_url":"https://api.github.com/repos/dulibrarytech/digitaldu-backend/issues/35/labels{/name}","comments_url":"https://api.github.com/repos/dulibrarytech/digitaldu-backend/issues/35/comments","events_url":"https://api.github.com/repos/dulibrarytech/digitaldu-backend/issues/35/events","html_url":"https://github.com/dulibrarytech/digitaldu-backend/issues/35","id":371958226,"node_id":"MDU6SXNzdWUzNzE5NTgyMjY=","number":35,"title":"scalability and performance with rearchitecture?PRJTASK0038842","user":{"login":"kimpham54","id":2915770,"node_id":"MDQ6VXNlcjI5MTU3NzA=","avatar_url":"https://avatars1.githubusercontent.com/u/2915770?v=4","gravatar_id":"","url":"https://api.github.com/users/kimpham54","html_url":"https://github.com/kimpham54","followers_url":"https://api.github.com/users/kimpham54/followers","following_url":"https://api.github.com/users/kimpham54/following{/other_user}","gists_url":"https://api.github.com/users/kimpham54/gists{/gist_id}","starred_url":"https://api.github.com/users/kimpham54/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kimpham54/subscriptions","organizations_url":"https://api.github.com/users/kimpham54/orgs","repos_url":"https://api.github.com/users/kimpham54/repos","events_url":"https://api.github.com/users/kimpham54/events{/privacy}","received_events_url":"https://api.github.com/users/kimpham54/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-10-19T13:29:28Z","updated_at":"2018-10-19T13:29:28Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"2018-08-07 10:48:09 - Kim Pham (Work notes)\n talked to Bill Branan (in an email thread), he confirmed that our proposed architecture will be fine in terms of scalability/performance. we should think about how to keep preservation masters separate from access copies, if that will improve performance, or if we should just be OK with whatever archivesdirect provides and how they partition their repository. also look into how to do stress testing (need a systems person to help with this)"}}
{"actor":{"display_login":"kimpham54"}}