⛔️ [DO NOT MERGE] ⛔️ feat: use FrontRemoteRenderer behind a switch #26556
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.
What is the value of this and can you measure success?
This allows us to use our new fancy Fronts rendering stack!
TL;DR; is that this removes the single point of failure with the current architecture, you can read more about that here and see the DCR part here.
This is a test, and ideally
DotcomRenderingService
should probably have thebaseUrl
as a non-optional string, but this feels like a nice first step.Hopefully we will be able to spin up the guessed-required amount of instances in DCR and up the test to monitor if we need to add more, or scale down.
Co-authored-by: Georges Lebreton [email protected]