experimental feat (container app environments): [topology] add multiple container app environments #12
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
hallihan
approved these changes
Feb 23, 2022
main.bicep
Outdated
| module env_shipping_dronedelivery 'environment.bicep' = { | ||
| name: 'env-shipping-dronedelivery' | ||
| // Drone Delivery App Environment Frontend | ||
| module env_shipping_dronedelivery_front 'environment.bicep' = { |
There was a problem hiding this comment.
Do we want to be more consistent with "frontend" "backend", instead of shortening to "front"?
ferantivero
force-pushed
the
expirment/add-2nd-cae
branch
from
7569a43
to
8918e20
Compare
…onments (#15) * adds why multiple environments narrative * Apply PR Feedback: improving wording, fixing typos and other contribs. Co-authored-by: Catherine Bundy <[email protected]>
ferantivero
changed the title
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.
WHY
Having
Ingestionservice separated from the rest of the underling services using a Service Bus queue in middle, it allow us to have two clearly separated local container app environments divided into Front and Backend. This is feasible becauseIngestionhas no direct communication with the underlaying service or sharing compute resources at all. Additionally, this separation could enable a better network topology in the future.WHAT Changed?
HOW to Test?
Follow the
READMEinstructions and you should be able to go thought the validation section and execute all the steps successfully.