Search the practice set
126 questions, 454 terms and 400 topics in 20 areas.
32 results for “Managed Services”
Managed Service Upgrade Window
The period during which a provider may apply patches or version upgrades to a managed service, usually involving a failover or brief unavailability.
Shared Responsibility Model
The division of duties between provider and customer, which shifts with the service model and is routinely misunderstood in the customer's disfavour.
Managed Service
A capability the provider operates — provisioning, patching, backup, scaling and failover — leaving you the configuration and the data.
Managed vs Self-Managed
Trading control, portability and unit cost against the operational burden of running the thing yourself.
Zonal vs Regional Services
Whether a cloud resource lives in one availability zone or is inherently spread across several — a property that determines what a zone failure takes with it.
API Gateway
A single entry point in front of a set of services that handles authentication, rate limiting, routing and protocol translation.
Airbnb's Service-Oriented Migration
Airbnb decomposed a large Rails monolith by first extracting a unified data-access layer, so that services were built on owned data rather than on shared database tables.
Backend for Frontend
A separate, narrow backend per client experience, which aggregates and reshapes downstream services for exactly that client's needs.
Cognitive Load
The total amount a team must hold in its head to work effectively, and a real constraint on how many services or domains one team can own.
Connection Proxy
A pooling layer between applications and a managed database that multiplexes many client connections onto a small number of database connections.
Contract Testing
Verifying that a provider satisfies the expectations each of its consumers actually relies on, without running all the services together.
Microservices
An architectural style where an application is a set of independently deployable services, each owning its data and aligned to a business capability.
NAT Gateway
A managed device that lets instances in a private subnet make outbound connections without being reachable inbound.
RED Method
A minimal per-service dashboard: Rate, Errors, Duration — the request-centric view of whether users are being served.
Saga
A sequence of local transactions across services where each step has a compensating action that semantically undoes it if a later step fails.
Server-Side Request Forgery
Inducing a server to make an HTTP request to an attacker-chosen destination, turning it into a proxy into networks and services the attacker cannot reach directly.
Tail Latency
The latency experienced by the slowest small percentage of requests, which is what users and dependent services actually feel.
XA Transaction
The X/Open standard interface for two-phase commit across heterogeneous resource managers, still common in enterprise middleware and rarely the right choice for new services.
A team wants to self-manage Kafka on Kubernetes to save money against the managed service. Evaluate.
The comparison they have probably made Instance cost versus managed service list price. That comparison usually favours self managing by a wide margin, and it o
A team shows you a design with eight services. Without knowing the domain, what questions tell you whether the boundaries are right?
What the interviewer is testing Whether you can evaluate a structure from its properties rather than needing to be a domain expert in every system you review. T
An estate has database passwords in environment variables across 200 services. Design the migration to a secrets manager.
Sequence it by risk, not by convenience Phase 0 — stop the bleeding. Secret scanning in CI and on the existing repositories, blocking new commits containing cre
Four services want four different databases: Postgres, MongoDB, Cassandra and Neo4j. What do you say?
The response: make each team justify it against a default Polyglot persistence is legitimate and routinely over applied. The question for each is not "is this d
Placing an order must reserve stock, charge the card and create a shipment across three services. Design it, and justify why not a distributed transaction.
First: question the boundary A transaction spanning three services often means one invariant has been split across three owners. Before designing a protocol, ch
Your services currently trust anything inside the VPC. A security review says move to zero trust. What changes, and what will it cost you?
What the interviewer is testing Whether "zero trust" is a concrete set of changes to you, or a slogan. What actually changes Workload identity. Every service ge
Managed Services
Which operational responsibilities actually transfer, and which do not.
Cloud Databases
Managed relational, key-value, document and analytical services.
Private Connectivity
Private endpoints, peering and dedicated links to managed services.
Managed vs Self-Managed
Trading control and unit cost against operational attention.
Domain Boundaries
Where the language of the business changes, and services should too.
Orchestration vs Choreography
A coordinator that knows the flow, or services that react to events.
Product Thinking
Treating platforms and services as products with users and a lifecycle.
Saga
Local transactions with compensating actions across services.