Shared Database Strategy and Schema Design

[Mkalbani]

Location: microservices/ (database configuration)
Labels: microservice, infrastructure, database
Estimated Time: 5 hours
Difficulty: Medium

Description

Design and implement database strategy for microservices including schema isolation, migrations, and database per service pattern.

Tasks

• Design database architecture (DB per service vs shared)
• Create separate schemas for each microservice
• Set up database migration system
• Configure connection pooling per service
• Implement read replicas for heavy services
• Add database backup strategy
• Create seed data scripts
• Document database conventions

Acceptance Criteria

• Each microservice has isolated schema
• Migrations run independently
• Connection pools optimized
• Backup strategy documented
• Database conventions clear

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 150 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[big14way]

@big14way has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

hi i am gwill i have contributed to stellar ecosystem and previously an od fellow i have 3 years experience in rust soroban
please assign me this issue its what i know how to do best

ℹ️ Repo Maintainers: To accept this application, review their application or assign @big14way to this issue.

[AlAfiz]

@AlAfiz has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hi! I would like to claim this issue to complete the infrastructure trilogy (Docker #66, Monitoring #70, and now Database).

Designing the database strategy is critical to prevent monolithic coupling. I will implement a "Database-per-Service" pattern using logical schema isolation within PostgreSQL to balance strict boundaries with resource efficiency.

My plan:

Architecture: Configure PostgreSQL with distinct Schemas (e.g., auth_schema, payment_schema) for each microservice to enforce isolation without the cost of multiple RDS instances.

Migrations: Set up a migration runner (likely via init-containers in Docker) to apply schema changes automatically on startup.

Pooling: Configure PgBouncer or service-level pooling to prevent connection exhaustion from multiple microservices.

Backups: Implement a pg_dump strategy that backs up schemas individually.

I am ready to start immediately.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @AlAfiz to this issue.

[drips-wave]

Congratulations, @AlAfiz! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on January 31, 2026.

🧑‍💻 @AlAfiz: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

⚠️ Important: When opening a PR, please link it to this issue to ensure it gets tracked accurately.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊