baarkerlounger
/
submit-social-housing-lettings-and-sales-data
mirror of https://github.com/communitiesuk/submit-social-housing-lettings-and-sales-data.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Submit social housing lettings and sales data (CORE)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
3052 Commits
218 Branches
260 Tags
83 MiB
 
 
 
 
Branch: CLDC-3611-performance-testing
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'CLDC-3611-performance-testing'
${ noResults }
submit-social-housing-letti.../docs/adr/adr-004-gov-paas.md

1.3 KiB
Raw Permalink Blame History

parent
Architecture decisions

004: Infrastructure switch to GOV.UK PaaS

The application infrastructure will be moved from the initial AWS set up to GOV.UK PaaS. The initial expectation is to have a GOV.UK PaaS account dluhc-core with 2 spaces sandbox, production.

Sandbox will consist of 2 small instances (512M) and 1 tiny-unencrypted-13 Postgres instance.

Production infrastructure sizing will be decided at a later time and once our account has been upgraded to a paid account.

The reasoning for this is:

  • Department policy is to use GOV.UK PaaS whenever possible
  • MHCLG does not have a lot of internal dev ops skills/capacity so by leveraging GOV.UK PaaS we can leverage having most of the monitoring, running, scaling and security already provided.
  • We get a simpler infrastructure setup than the AWS setup we currently have
  • All of the infrastructure we currently require is well supported on GOV.UK PaaS

One potential downside is that data replication to CDS may be slightly more complicated as adding our database to a VPC requires the Gov PaaS support team to do that on our behalf.

This also means the GitHub repository previously used for Infrastructure will be archived after this change goes in as it won’t be needed any more.