Concepts in DevOps & Cloud, page 29
Traffic Splitting: Route Live Traffic Between Service Versions
Traffic splitting directs percentages of live user traffic to different versions of a service. It's key for canary releases, letting you test new code on a small user group before a full rollout.
Cloud Business Case: Justifying Your Move to the Cloud
A cloud business case translates technical goals into financial terms like ROI and TCO to win executive support. It's the "why" and "how much" for a migration, used to secure budget and sponsorship.
Platform API: The Contract for Your Developer Platform
The Platform API is the central contract for your internal developer platform, abstracting complex tooling into simple, self-service actions. It's what a developer portal or CLI calls to provision a database or scaffold a new service without knowing the…
Content-Based Routing: Directing Traffic by Request Details
Content-based routing is a smart traffic cop for your services. It inspects request headers or URIs to direct traffic, enabling canary releases or A/B tests. The footgun is rule order: a broad rule placed first can shadow specific rules below it.
Cloud Center of Excellence (CCoE): Your Internal Cloud Guides
A Cloud Center of Excellence (CCoE) is your company's internal cloud consulting team, centralizing expertise to guide adoption. It creates reusable patterns, manages costs, and ensures security, helping large orgs scale.
Crossplane: The Kubernetes Control Plane for Infrastructure
Crossplane turns your Kubernetes cluster into a universal control plane for all your cloud infrastructure, not just containers. Use it to let developers provision cloud resources like databases using familiar kubectl commands.
Service Mesh Authorization: A Bouncer for Your Microservices
A service mesh authorization policy is a bouncer for your microservices. It moves access control from your app to the mesh, checking service identity and request details like HTTP method and path. Use it for fine-grained, Zero Trust security.
Cloud Landing Zone: A Blueprint for Cloud Environments
A Cloud Landing Zone is a pre-configured, secure foundation for your cloud applications, like a city grid with utilities ready for new buildings. It provides shared services like networking and identity, ensuring consistency for large organizations.
Score: Define Your Workload Once, Run Anywhere
Score is a universal remote for your workload configs, letting you define what your app needs once in a score.yaml file. It translates this spec into files for Docker Compose or Kubernetes, preventing config drift.
Retry and Timeout Policies: Handling Network Flakes
Retries and timeouts are automated patience for network requests. Instead of failing on a glitch, a service waits (timeout) and tries again (retry). This is key for microservice resilience, but beware of "retry storms" that can amplify failures.
What is Cloud Native Architecture?
Cloud Native refers to a collection of practices and open-source projects, like Kubernetes, governed by the CNCF. It's used by enterprises to build modern products and services.
Visual Regression Testing: Catching Unintended UI Changes
Visual regression testing is a 'spot the difference' game for your UI, comparing screenshots to a baseline to catch visual bugs. It's used in CI/CD to prevent CSS regressions and layout breaks that unit tests miss.
Circuit Breaker Pattern: Fail Fast, Not Hard
A circuit breaker wraps network calls to prevent cascading failures. It monitors for errors, and if a service seems down, it 'trips' to fail requests instantly without hitting the network. This gives the failing service time to recover.
Docker Image Tagging: A Strategy for Reliable Deployments
Think of Docker tags as pointers, not permanent labels. Multiple tags like v1.2.3 and production can point to the same image SHA, enabling reliable CI/CD and rollbacks. The footgun is relying on mutable tags like latest in production.
Traffic Mirroring: Test in Production, Safely
Traffic mirroring copies live production requests to a new service without affecting the user's response. It's used to test new code with real traffic before a full rollout. The main footgun is accidentally duplicating writes or other stateful actions.
The Sidecar Pattern: Offload and Isolate Application Logic
The Sidecar Pattern attaches a helper container to your main application, like a sidecar on a motorcycle. It offloads tasks like logging or proxying, letting you add features without changing the main app's code. The footgun is over-engineering a solution.
Hotfix Deployment: Emergency Production Patches
A hotfix is a surgical strike on a production bug, using a dedicated branch to isolate the emergency fix. It's used for critical security flaws or severe defects that can't wait. The footgun: forgetting to merge the fix back into main, causing the bug to.
Egress Gateway: Control Your Mesh's Outbound Traffic
An Egress Gateway is a monitored exit door for all outbound traffic from your service mesh. Use it to enforce security on external calls, like restricting domains or originating mTLS.
The Ambassador Pattern: Your App's Diplomatic Sidecar
The Ambassador pattern places a proxy next to your application to handle its network communication, like a diplomat. This adds modern features like monitoring, security, and retries to legacy apps or across languages without changing app code.
Configuration Hydration: From Template to Manifest
Configuration hydration turns templates like Helm charts into final Kubernetes manifests. This lets you see the exact YAML diff in a PR, not just a variable change. The footgun is that this adds a build step which, if broken, blocks all deployments.
We are hiring for this. Every open role lists the topics its interview covers, so you can prepare for the real thing rather than guessing.
See open roles