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.

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

[FEAT] Merge CMS with Database #22

Closed
kkopanidis opened this issue Feb 8, 2022 · 0 comments · Fixed by #53
Closed

[FEAT] Merge CMS with Database #22

kkopanidis opened this issue Feb 8, 2022 · 0 comments · Fixed by #53
Labels
discussion enhancement New feature or request

Comments

@kkopanidis
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Currently conduit spins up multiple containers that don't really make sense to be separate, since they can't practically scale independently. Once such pair is CMS and Database. All CMS operations require the database and request increase in CMS is in a 1:1 relation with request increases in the Database.

Describe the solution you'd like
The proposal is to merge the 2 modules, and basically make all of the CMS functionality part of the database functionality.

Additional context
Something we should look out for is the breaking URL issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant