Search the practice set
126 questions, 454 terms and 400 topics in 20 areas.
9 results for “Coupling”
Coupling
The degree to which one component must know about, or change alongside, another.
Synchronous vs Asynchronous Communication
Whether the caller waits for the callee's answer — decided by whether the caller's outcome depends on it, not by latency or taste.
A downstream team needs to react to order changes. The order service can publish events, or they can consume CDC from its database. Which, and why?
The recommendation: published events, with CDC as the mechanism if needed The distinction that matters is what the consumer becomes coupled to . CDC consumed di
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 order service must notify inventory, billing, shipping and analytics when an order is placed. Synchronous calls or events? Justify your choice per consumer.
What the interviewer is testing Whether you apply the decision per interaction rather than adopting one style globally. The framing that matters Synchronous cal
When should a service call another synchronously, and when should it publish an event instead? Give me the deciding test, not a preference.
The deciding test Does this user action succeed or fail based on this callee's response? If yes, the call is synchronous, because you need the answer to decide.
Coupling
How much one component must know about, or change alongside, another.
Change Data Capture
Turning a database's replication log into a stream, and its coupling risk.
Embeddings
Dense representations, model coupling and the migration they imply.