Design: Shared database layer for hosted applications - #69
Open
nkakadiya4 wants to merge 3 commits into
Open
Conversation
jamesiarmes
requested changes
Jul 23, 2026
jamesiarmes
left a comment
jamesiarmes
left a comment
Member
There was a problem hiding this comment.
Overall design is nice; I especially appreciate the per-server rather than per-app user scoping. Adding a control plane for our hosting service is great idea, but a bit more than we're looking to engineer right now.
Check the comments below, but the largest change will be use OpenTofu rather than a dedicated control plane.
jamesiarmes
requested changes
Jul 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposes replacing per-app dedicated MSSQL clusters with a shared database layer: shared-by-default PostgreSQL clusters (dedicated mode opt-in), IAM-only auth, per-service DB roles, schema-per-app isolation, and a new
database:app spec block with standardDB_*env vars (no password).