Spike on fluent ConnectionFactory configuration API #1242
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 ConnectionFactory class has dozens of parameters. It can be overwhelming to configure, especially
for tricky topics like TLS where the parameters are among the other dozens, without clear way to find them.
This commit introduces an API to simplify the configuration of ConnectionFactory. It is fluent, uses modern API (e.g. Duration for timeout), and groups common settings in sub-API.
The configuration API will be introduced in 5.x, marked as experimental, and refined in minor releases.
The traditional setter-based API will be marked deprecated 6.x and removed in 7.x.
Benefits of the new configuration API:
References #608, #1139
There is a demo class to show the differences between the regular and new API.