Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Split datastore into service-specific databases #7

Open
mattbonnell opened this issue May 21, 2020 · 0 comments
Open

Split datastore into service-specific databases #7

mattbonnell opened this issue May 21, 2020 · 0 comments
Assignees
@mattbonnell
Labels
enhancement New feature or request infra Pertains to the app's infrastructure

Comments

@mattbonnell
Copy link
Contributor

We'd enjoy greater availability, reliability and scalability if each service had its own database cluster. The question remains, to manage storage ourselves in cluster or to outsource it to a managed DB service (Google Cloud SQL)?
@mattbonnell mattbonnell added enhancement New feature or request infra Pertains to the app's infrastructure labels May 21, 2020
@mattbonnell mattbonnell self-assigned this May 21, 2020
@mattbonnell mattbonnell changed the title Currently all services are sharing one database for simplicity. Desired end state is that they each have their own Split datastore into service-specific databases May 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mattbonnell mattbonnell

Labels
enhancement New feature or request infra Pertains to the app's infrastructure
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mattbonnell