Risks
|
Impact
|
Probability
|
Detail
|
Depending on third party provider
|
High
|
Low
|
This project depends on third party data aggregators. The system will be useless if those data providers refuse to provide data.
|
Partnership with other small provider
|
Medium
|
Medium
|
Risk can be associated with the partnership of GlocoHCP with Nursing, and Ambulatory Care provider. In case those people refuse to join the initiatives, it will be difficult to manage the operation.
|
Marketing and User subscription
|
High
|
High
|
If marketing fails to bring customers, this project will not return back its investment.
|
DevOps skills shortage
|
High
|
Medium
|
Required to build internal resources for DevOps.
|
Significant Operations overheads
|
Medium
|
High
|
Properly plan microservices so that it will not be too granular.
|
Duplication of effort
|
Medium
|
High
|
Each microservice needs data and rules, which can be duplicated among many services if it is not maintained.
|
Distributed system complexity
|
Medium
|
High
|
Maintain guidelines and principles with effective tool chains.
|
Testability challenges
|
High
|
High
|
Idiomatic microservices involves placing less emphasis on testing and more on monitoring so we can spot anomalies in production and quickly rollback or take appropriate action.
|
Asynchronicity is difficult
|
Medium
|
High
|
Manage asynchronous operation using event notification rather than process notification.
|
Operational teams will be assigned a CTASK (change task) in ServiceNow once the change is approved. The CTASK will specify the exact steps to make the change, the back out plan (or Fail Forward26 plan), and the change window.