mirror of
https://github.com/cisagov/manage.get.gov.git
synced 2025-07-20 17:56:11 +02:00
Cloud.gov ADR (#61)
* add cloud.gov adr * talk about alternatives considered
This commit is contained in:
parent
5e4c44a444
commit
bcda825a6b
1 changed files with 25 additions and 0 deletions
25
docs/architecture/decisions/0006-cloud-gov.md
Normal file
25
docs/architecture/decisions/0006-cloud-gov.md
Normal file
|
@ -0,0 +1,25 @@
|
|||
# 6. Cloud.gov
|
||||
|
||||
Date: 2022-08-12
|
||||
|
||||
## Status
|
||||
|
||||
Accepted
|
||||
|
||||
## Context
|
||||
|
||||
We need a place to run our application for the registrar. Cloud.gov is a FIMSA Moderate Fedramped solution that supports our language and framework selections.
|
||||
|
||||
## Decision
|
||||
|
||||
To use cloud.gov to host our application(s).
|
||||
|
||||
## Consequences
|
||||
|
||||
Choosing cloud.gov for our solution means we are locked into its opinionated choices for our infrastructure. It forces us to run 12-factor applications. It doesn't support brokering for services we may need like email notifications.
|
||||
|
||||
It also means the compliance lift is much lighter. We do not need to prove we are compliance for the majority of our infrastructure and our runtime enviornment.
|
||||
|
||||
## Alternatives Considered
|
||||
|
||||
Run our application on in either CISA's Azure or AWS environment with a continerized deployment.
|
Loading…
Add table
Add a link
Reference in a new issue