Prep for clustering functionality #204
Merged
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.
The prep work for clustering (primarily refactoring) moved into a separate PR for clarity. This includes:
Config
class to surface-level helper only. Separate "settings" classes have now been added to manage separation of concerns and management of defaults more sensibly. Significant new classes here areConnectionSettings
,SecurityPlan
andPoolSettings
.bolt
scheme to describe current behaviour as opposed to future behaviours, such as discovery. The classInternalDriver
class is now calledDirectDriver
as we will end up with multipleDriver
implementations.SecurityPlan
class. This means that some of the behaviour that was previously executed lazily (such as validating certificates) is now done eagerly and will therefore fail sooner on error.