Search the practice set
126 questions, 454 terms and 400 topics in 20 areas.
60 results for “Event-Driven Architecture”
Event-Driven Architecture
A style in which components communicate by emitting and reacting to facts about what happened, rather than by calling each other.
Event Sourcing
Storing the full sequence of state-changing events as the system of record, and deriving current state by replaying them.
Event-Driven Integration
Systems integrating by publishing and consuming events rather than by calling each other's APIs.
Domain-Driven Design
Modelling software around the business domain, with boundaries drawn where the language of the business changes.
Salesforce's Metadata-Driven Multi-Tenancy
Salesforce serves every customer from shared infrastructure with a single physical schema, storing customer-specific data structures as metadata rather than as separate tables.
SQL vs NoSQL
A choice driven by access patterns, consistency requirements and query flexibility — not by data volume, which is the reason usually given.
Architecture Cost Model
A calculation, made during design, of what an architecture will cost to run at expected and at peak volume.
Architecture Decision Log
The ordered, immutable collection of a system's decision records, read as a history rather than as a specification.
Architecture Decision Record
A short, immutable document capturing one architectural decision, its context, the alternatives, and its consequences.
Architecture Principle
A durable, agreed rule that constrains design decisions in advance, stated with its rationale and its implications.
Architecture Review Board
A forum that reviews significant designs against standards, risks and strategy before commitment.
Architecture Style
A named, coarse-grained way of organising a whole system, as distinct from a pattern that solves one recurring problem inside it.
Architecture Trade-off Analysis Method
A structured evaluation that scores an architecture against prioritised quality-attribute scenarios and identifies the points where those attributes conflict.
Cell-Based Architecture
Partitioning a service into complete, independent copies of itself, each serving a subset of customers, so a failure is bounded to one cell.
Clean Architecture
Concentric layers with a strict dependency rule — source code dependencies point only inwards, towards higher-level policy.
A service writes to its database and then publishes an event to Kafka. Sometimes consumers see an event for a record that does not exist, and sometimes a record exists with no event. Why, and how do you fix it?
What the interviewer is testing Recognition of the dual write problem — one of the most common defects in event driven systems and one that testing rarely catch
A design review presents a new event-driven platform. What cost questions do you ask before approving it?
What the interviewer is testing Whether cost is part of your architecture review or an afterthought handled by finance later, and whether you know the specific
Orders must trigger inventory reservation, a confirmation email, an analytics record and a fraud check. Queue, topic, or both — and what breaks if you choose wrong?
What the interviewer is testing Whether you know the difference between work distribution and notification — a distinction that produces one of the most confusi
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.
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
A 43-second network partition caused GitHub over 24 hours of degraded service in 2018. How does a 43-second event become a day-long incident?
The case, as publicly reported On 21 October 2018, routine maintenance replacing failing optical equipment caused a 43 second loss of connectivity between GitHu
A team wants event sourcing for a new order service, citing audit requirements. What do you recommend?
The recommendation: probably an audit log, not event sourcing If the requirement is audit , event sourcing is a very expensive way to obtain it. An append only
Event-Driven Architecture
Publishing facts, and trading comprehensibility for decoupling.
Event-Driven Integration
Publishing facts rather than commands, and versioning event schemas.
Serverless vs Containers
Spiky and event-driven versus sustained throughput.
Domain-Driven Design
Ubiquitous language, bounded contexts and context mapping.
Event Sourcing
Storing the change log as the system of record, and what that costs forever.
Event Sourcing
The event log as the system of record, with state as a projection.
Outbox
Making the event atomic with the business write it describes.
Single vs Multi-Region
Driven by RTO, RPO and residency rather than by ambition.
AI-Era Architecture
General material on architecting systems that include models.
Application Architecture
The application estate as a designed portfolio rather than an accumulation.
Architecture Communication
General material on communicating architecture.
Architecture Cost Modelling
Pricing a design before building it, at expected and at ten times volume.
Architecture Decision Records
One decision, its context, alternatives and consequences, kept immutable.
Architecture Decision-Making
General material on making and recording architectural decisions.
Architecture Diagrams
Choosing an audience and refusing to mix levels of abstraction.
Architecture Documentation
What to write down, at what altitude, and what nobody will ever read.
Architecture Fundamentals
General material on what solution architecture is and what an architect is accountable for.
Architecture Governance
Preventive, automated controls rather than review meetings.
Architecture Patterns
General material on architectural patterns and their trade-offs.
Architecture Principles
Durable agreed rules that rule options out, stated with rationale and implications.
Architecture Review Boards
Thresholds, early engagement and a real route to accept deviation.
Architecture Reviews
Reviewing early enough to influence rather than to veto.
Architecture Roadmaps
Sequencing change across an estate with dependencies and funding.
Architecture Roles
Solution, enterprise, domain and platform architecture, and where each is accountable.
Architecture Styles
System-level organising shapes, and how they differ from problem-level patterns.
Business Architecture
General material on the business side of architecture.
Cell-Based Architecture
Complete isolated copies each serving a subset of customers.
Clean Architecture
Concentric layers with dependencies pointing only inwards.
Cloud Architecture
General material on designing for cloud platforms.
AI-Era Architecture
AI workloads meeting security, data, networking, reliability and cost.
API & Integration Architecture
Contracts between systems, and the compatibility discipline that keeps them working.
Architecture Communication
Explain the same architecture to a CEO, an engineering manager and an engineer.
Architecture Decision-Making
Where senior engineer becomes architect: evaluate, choose, write it down.
Architecture Fundamentals
What architecture actually is: drivers, constraints, trade-offs and the principles behind them.
Architecture Patterns
Patterns as tools for recurring problems, with forces and consequences.
Business Architecture
Connecting technology decisions to the outcomes that fund them.
Cloud Architecture
Cloud as a set of architectural capabilities, not a catalogue of service names.
Cost Architecture & FinOps
Architecture is also economics; exceptional architects can price their designs.