-
Notifications
You must be signed in to change notification settings - Fork 0
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
Rework to use real database #133
Labels
enhancement
New feature or request
Comments
Later we could move to a managed MySQL cluster, provided by OCI. |
This was referenced May 17, 2024
Merged
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using bucket files as database is showing its limitations. Not only is it slow, but it also limits our possibilities to retrieve data. Currently this is fine for most situations, but we already receive timeouts for repos with many builds. So we'd better replace this with a "real" database, like MySQL.
MySQL also supports JSON fields, so we could store the more dynamic parts of the entities (like job configuration and results) in JSON. The biggest drawback is that we become dependent on another external service, although it may be better than the current solution (file storage).
The text was updated successfully, but these errors were encountered: