As a developer of notify, I want to make sure that our infrastructure is suitable for our load so that we can deliver a stable product that is easy to maintain and cost effective.
As a technical principal steward of the CDS organization,
I want to document our technological choices,
So that I can explain for it to the rest of the organization
And leave some traces behind.
WHY are we building?
There has been some suggestion that Kubernetes may be overkill for notify. We should investigate all of the available solutions and determine the pros and cons of each
WHAT are we building?
ADR documenting the different deployment methods for Notify and which would be best.
VALUE created by our solution
Documenting for the organization and the team, explaining our technological choices.
Acceptance Criteria
[ ] Have a section on our experience with moving the API to lambdas (attachments size reduced, NewRelic not easy on integration and tracking metrics, database connections, etc...).
[ ] Have a section on moving all to lambdas: pros, cons, cost and risk.
[ ] Have a section on moving all to kubernetes: pros, cons, cost and risk.
[ ] Have a "meet in the middle" section to move some to lambdas, and other to kubernetes (what about moving API back to kubernetes?).
QA Steps
[ ] Reviewed by the platform team (security, Core, SRE, Notify teams).
Description
As a developer of notify, I want to make sure that our infrastructure is suitable for our load so that we can deliver a stable product that is easy to maintain and cost effective.
As a technical principal steward of the CDS organization, I want to document our technological choices, So that I can explain for it to the rest of the organization And leave some traces behind.
WHY are we building?
There has been some suggestion that Kubernetes may be overkill for notify. We should investigate all of the available solutions and determine the pros and cons of each
WHAT are we building?
ADR documenting the different deployment methods for Notify and which would be best.
VALUE created by our solution
Documenting for the organization and the team, explaining our technological choices.
Acceptance Criteria
QA Steps