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

cloud: Split deployment control into functions instead of services #518

Open
spbnick opened this issue Apr 19, 2024 · 0 comments
Open

cloud: Split deployment control into functions instead of services #518

spbnick opened this issue Apr 19, 2024 · 0 comments

Comments

@spbnick
Copy link
Collaborator

spbnick commented Apr 19, 2024

At the moment, the deployment done with the cloud script can be split and controlled on Google Cloud service type boundaries (roughly). That was working quite well, but as the complexity of the deployment is growing, we need to consider splitting the deployment along functional boundaries. I.e. instead of "cloud functions", "pub sub", "postgresql", etc. split by function, such as "operational database", "archive database", "ingestion", "update processing", "notification generation", and so on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant