Search the practice set
126 questions, 454 terms and 400 topics in 20 areas.
60 results for “Enterprise Integration”
Enterprise Integration Patterns
A catalogue of named, composable messaging patterns — router, translator, aggregator, splitter, filter, dead letter channel — that gives integration work a shared vocabulary.
Event-Driven Integration
Systems integrating by publishing and consuming events rather than by calling each other's APIs.
API Gateway
A single entry point in front of a set of services that handles authentication, rate limiting, routing and protocol translation.
Anti-Corruption Layer
A translation layer that converts a legacy or external system's model into your own, so its concepts do not leak into your domain.
Application Portfolio Management
Maintaining an inventory of every application with its owner, cost, business value and technical health, and using it to decide what to invest in, replace or retire.
Architecture Review Board
A forum that reviews significant designs against standards, risks and strategy before commitment.
Backward Compatibility
The property that a new version of a producer continues to work with clients written against the old version.
Business Capability
What a business does, expressed stably and independently of how it currently does it or who is responsible.
CI/CD
Merging work continuously into a shared trunk with automated verification, and keeping every commit in a state that could be released.
Capability Map
A structured view of everything a business does, used as the stable frame for mapping applications, investment, ownership and gaps.
Capital One's Data Centre Exit
A major US bank closed all eight of its data centres and moved fully to public cloud, treating governance automation as the enabling technology rather than a constraint.
Change Data Capture
Publishing a stream of a database's row-level changes by reading its replication log, without modifying the application that owns it.
Contract Testing
Verifying that a provider satisfies the expectations each of its consumers actually relies on, without running all the services together.
Dead Letter Queue
A separate queue that receives messages which could not be processed after a set number of attempts, so they neither block the consumer nor disappear.
GraphQL
A query language and runtime where the client specifies exactly which fields it needs, against a typed schema, usually via a single endpoint.
Idempotency Key
A client-generated unique value sent with a request so the server can recognise a retry and return the original result instead of acting twice.
LinkedIn and the Origin of Kafka
Kafka was built to replace point-to-point data integration between many systems with a single durable log that any system could publish to and any number could read.
Model Context Protocol
An open protocol that standardises how AI applications connect to external tools, data sources and prompts.
OpenAPI
A machine-readable specification format for HTTP APIs, from which documentation, clients, servers, mocks and validation can be generated.
Paved Road
A supported, opinionated default way to build and run a service, made easy enough that teams choose it rather than being required to.
REST
An architectural style for APIs built on resources identified by URLs, manipulated with uniform HTTP methods, and stateless requests.
Run a threat model on a new payment integration: our service calls a third-party payment provider and receives webhooks. Where are the interesting threats?
Draw the boundaries first Three trust boundaries, and nearly every interesting threat lives on one of them: 1. User → our service (untrusted input, authenticate
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 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
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
Enterprise Integration
Estate-wide integration strategy, standards and shared infrastructure.
API & Integration
General material on integrating systems through contracts.
Enterprise Architecture
General material on architecture at portfolio and estate scale.
Event-Driven Integration
Publishing facts rather than commands, and versioning event schemas.
Integration Patterns
Routers, translators, splitters, aggregators and dead letter channels.
Legacy Integration
Reaching systems that cannot change, without importing their model.
Legacy Integration Patterns
Anti-corruption layers, adapters and CDC against systems that cannot change.
Partner & B2B Integration
External contracts, onboarding, sandboxes and long deprecation windows.
API Documentation
OpenAPI as a machine-checked contract rather than as prose.
API Error Handling
Error shapes, retryability signals and machine-readable causes.
API Versioning
URL, header and account-pinned versioning, and who carries the burden.
APIs as Products
Ownership, lifecycle, deprecation policy and developer experience.
Application Architecture
The application estate as a designed portfolio rather than an accumulation.
Application Portfolio Management
Inventory, ownership, cost and health for every application.
Application Rationalisation
Retire, consolidate, replatform — and why retirement is under-applied.
Architecture Governance
Preventive, automated controls rather than review meetings.
Architecture Review Boards
Thresholds, early engagement and a real route to accept deviation.
Architecture Roadmaps
Sequencing change across an estate with dependencies and funding.
Architecture Roles
Solution, enterprise, domain and platform architecture, and where each is accountable.
Backward Compatibility
Which changes are safe, and how to make breakage a build failure.
CI/CD
Continuous integration and delivery, and the architecture that caps them.
Capability Maps in EA
The stable frame for hanging investment, ownership and health off.
Contract Testing
Verifying what consumers actually rely on, without a shared environment.
EA Domains
Business, application, data and technology architecture as viewpoints.
EA Frameworks
Zachman, FEAF and others — vocabulary rather than method.
EA Metrics
Measuring whether architecture work changed anything.
GraphQL
Client-specified queries, N+1 resolution and query-cost control.
Idempotency Keys
Client-generated keys stored atomically with the operation they guard.
InnerSource
Open-source collaboration practices applied inside an organisation.
Message Formats
JSON, Protobuf, Avro — schema evolution and payload economics.
Pagination & Filtering
Offset versus cursor, stable ordering and unbounded result sets.
Paved Roads
Making the supported path the easiest path, with a way to leave it.
Platform Teams
Reducing other teams' cognitive load, measured by adoption.