Enable Custom Database Connections for Health Data #216
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
❤️ |
eusonlito
changed the title
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi! This PR introduce the capability for the EloquentHealthResultStore to support a different database connection to store the data.
The primary motivation behind this enhancement is to enable applications to maintain a clean and focused main database by offloading monitoring logs to a separate database. In many applications, especially those with high traffic or complex data structures, the main database is optimized for performance and critical operations. Monitoring logs, while essential for maintaining the health and performance of the application, can quickly grow in size and potentially clutter the main database. This can lead to decreased performance and complicate database maintenance tasks.
Regards!