Repository navigation
Labs 02–04: Key ideas before the steps, real-world uses after - #19
Merged
Merged
Conversation
Signed-off-by: Ante Projić <[email protected]>
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
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.
Same pattern as Lab 01 (#18).
compose.yaml, service discovery by DNS name, separate lifecycles. Written so it doesn't give away the Part 3 predictions, the Redis exposure question or the--scalequestion. Real world: local development, Kubernetes, managed databases.img/who-manages.png), a VM as several billed resources, everything is an API call, billing while allocated, activity log. Real world: EC2/Compute Engine, Terraform (Lab 06), scale sets and auto scaling groups.All doc links checked (200). No change to steps, timings or submissions. Lab 03 was already tight at ~44 min; the Key ideas add ~3 min of reading.