89 databaseoperations should handle connection failures gracefull #92
Conversation
This file contains hidden or 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
…d error handling - Introduced resilience policies for database operations, including retry and circuit breaker mechanisms. - Added IPolicyFactory interface and PolicyFactory class to encapsulate policy creation. - Enhanced PostgreSqlCacheOptions with configuration options for resilience patterns. - Refactored existing database operation methods to utilize new resilience execution methods. - Validated resilience configuration options to ensure proper setup.
…stency - Changed target framework in CachingTest.csproj from net6.0 to net8.0. - Refactored test methods in DatabaseExpiredItemsRemoverLoopTests and DatabaseOperationsAdditionalTests to use synchronous methods instead of asynchronous ones for better clarity and consistency. - Updated comments in tests to reflect resilience behavior when using invalid connection strings. - Added new tests for resilience patterns in DatabaseOperationsResilienceTests and DatabaseResilienceIntegrationTests. - Introduced new tests for policy creation in PolicyFactoryTests and validated PostgreSqlCacheOptions for resilience configurations.
- Updated DatabaseOperationsAdditionalTests to focus on unique scenarios. - Renamed test method for constructor verification to better reflect its purpose. - Removed outdated tests related to cache item operations that were deemed unnecessary. - Added new tests for cache item expiration scenarios in DatabaseOperationsTests to ensure comprehensive coverage.
… handling - Updated DatabaseOperations to remove redundant exception handling when resilience patterns are disabled, allowing direct execution of operations. - Refactored PolicyFactory to enhance logging behavior based on resilience options and adjusted the order of policy wrapping to conditionally include circuit breaker functionality. - Added validation in PostgreSqlCacheOptions to log warnings when resilience sub-options are configured without enabling resilience patterns.
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.
No description provided.