Deployment Plan and Infrastructure
We plan to follow the following roll-out strategy, adapted for our use case (because this is an internal tool, it won't see consumption by the stakeholder's clients).
- Release to stakeholder
- Release to development team's family and friends
- Release to other users at the stakeholder's company
We follow continuous deployment and trunk-based development, so there are not specific versions for specific users. We will always be collecting feedback based on the latest version.
The stakeholder has indicated that they want to deploy to AWS, so we have provided an AWS CDK template which can be used to deploy the project and its dependencies (Postgres, etc.) to AWS in a containerized environment (AWS Elastic Container Service). Pictured below is a flow diagram for the deployment plan under AWS:
In our initial testing, the AWS-deployed version will cost around $47.10/month to operate, so for the version that we host over the life of the project, we plan to use the server which will be provided by CSSE. On that server we will host Postgres, Loki, Promtail, Grafana, and the frontend and backend using Docker containers. The plan is to continuously deploy from our main branch to this server. We have not gained access to the CSSE server as of writing.