PR deployments
Date: 2025-01-12
Status: accepted
Context
As we plan the database setup, we quickly ran into a key question: how should we handle PR deployments? Provisioning an Aurora database for every pull request could become expensive and slow, both in cost and in lead time.
Decision
For now, we will not deploy the backend application for pull requests. Instead, we will build the app, run static analysis, and execute the full test suite. Most importantly, we aim to establish strong contract testing. PR deployments tend to provide the most value for UI/frontend applications; for a pure backend/API service, we consider them less critical at this stage.
Consequences
Some issues may only surface in staging—especially around database migrations. This is a trade-off we acknowledge and will need to manage through process and testing improvements.
If PR deployments later prove beneficial for a specific use case, we will revisit this decision and explore an approach that is both time- and cost-efficient.