Open forkfork opened 3 years ago
When creating a microservice, the database should be encapsulated within that service - and not exist outside of it.
I think it's important to separate the service and database lifecycle. If you delete a service, the database should probably persist. Having a separate attach / detach process would make it harder to accidentally delete a database.
When creating a microservice, the database should be encapsulated within that service - and not exist outside of it.
I think it's important to separate the service and database lifecycle. If you delete a service, the database should probably persist. Having a separate attach / detach process would make it harder to accidentally delete a database.
Agree from an operational / resiliency perspective - but separating the two does encourage blurring of bounded contexts. This is one of the most critical features of the Heroku platform, and could be a good fit for App Runner potentially.
Tell us about your request I would like to be able to attach an SQL database to my App Runner service from within the App Runner interface / YAML / API, and automatically gain private connectivity to this database from my service.
Describe alternatives you've considered I could use Copilot for this, or I could use CDK - but those involve a lot of steep learning curves.
Additional context When creating a microservice, the database should be encapsulated within that service - and not exist outside of it.