{"action":"opened","issue":{"url":"https://api.github.com/repos/USEPA/E-Enterprise-Portal/issues/42","repository_url":"https://api.github.com/repos/USEPA/E-Enterprise-Portal","labels_url":"https://api.github.com/repos/USEPA/E-Enterprise-Portal/issues/42/labels{/name}","comments_url":"https://api.github.com/repos/USEPA/E-Enterprise-Portal/issues/42/comments","events_url":"https://api.github.com/repos/USEPA/E-Enterprise-Portal/issues/42/events","html_url":"https://github.com/USEPA/E-Enterprise-Portal/issues/42","id":191033899,"number":42,"title":"SPIKE: Investigate how to make Portal fault tolerant when partner applications/services fail.","user":{"login":"e-enterprise-portal-team","id":20970620,"avatar_url":"https://avatars.githubusercontent.com/u/20970620?v=3","gravatar_id":"","url":"https://api.github.com/users/e-enterprise-portal-team","html_url":"https://github.com/e-enterprise-portal-team","followers_url":"https://api.github.com/users/e-enterprise-portal-team/followers","following_url":"https://api.github.com/users/e-enterprise-portal-team/following{/other_user}","gists_url":"https://api.github.com/users/e-enterprise-portal-team/gists{/gist_id}","starred_url":"https://api.github.com/users/e-enterprise-portal-team/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/e-enterprise-portal-team/subscriptions","organizations_url":"https://api.github.com/users/e-enterprise-portal-team/orgs","repos_url":"https://api.github.com/users/e-enterprise-portal-team/repos","events_url":"https://api.github.com/users/e-enterprise-portal-team/events{/privacy}","received_events_url":"https://api.github.com/users/e-enterprise-portal-team/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-11-22T15:13:47Z","updated_at":"2016-11-22T15:13:47Z","closed_at":null,"body":"Load locally? - Don't move to loading locally just because one library failed \r\nGive widgets 5 seconds to load, and don't load item at all if failed. \"Fail gracefully\" \r\n\r\nNeed to further discuss in the discovery sprint - what to do when remote services are not behaving.\r\nGet rid of user impact and produce diagnostic information when a failure occurs.\r\n\r\n*Assumptions:*\r\n# There are no firewall restrictions for accessing partner services\r\n# We are not addressing how to handle invalid data, only connection failure / timeout\r\n# We are allowed to store cached data on our servers as necessary: no privacy / confidentiality concerns\r\n# There are no specific requirements on diagnostic information when a failure occurs"}}
{"actor":{"display_login":"e-enterprise-portal-team"}}