A minimal system for orchestration and CI/CD will need to be in place.
Further details can be worked out down the line, but we would like to use Google Cloud Build for CI/CD and Google App Engine for deploying, scaling, and monitoring the application.
It has been suggested that we use docker with "decoupled and stateless architect components" for potential integrations with Kubernetes down the line. I'll have to look further into this when the time comes to learn more about the options and choose the most fitting.
Performance and scalability:
For basic matters of performance and scalability, Google App Engine’s built in functionality will likely be sufficient. Server load and memory should not be an issue since almost all functionality is client side and no data is ever stored. Page load times and validator runtimes should be monitored to maintain a high-quality UX.
TL;DR
A minimal system for orchestration and CI/CD will need to be in place.
Further details can be worked out down the line, but we would like to use Google Cloud Build for CI/CD and Google App Engine for deploying, scaling, and monitoring the application.
It has been suggested that we use docker with "decoupled and stateless architect components" for potential integrations with Kubernetes down the line. I'll have to look further into this when the time comes to learn more about the options and choose the most fitting.
Performance and scalability: