Search the practice set
126 questions, 454 terms and 400 topics in 20 areas.
50 results for “Partner & B2B 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.
Backward Compatibility
The property that a new version of a producer continues to work with clients written against the old version.
CI/CD
Merging work continuously into a shared trunk with automated verification, and keeping every commit in a state that could be released.
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.
REST
An architectural style for APIs built on resources identified by URLs, manipulated with uniform HTTP methods, and stateless requests.
Rate Limiting
Bounding how many requests a caller may make in a window, to protect capacity and enforce fair use.
Stripe's API Versioning
Stripe pins each account to the API version current when it integrated and transforms requests and responses between versions internally, so integrations never break and the core …
Test Pyramid
A distribution of tests weighted towards many fast unit tests, fewer integration tests, and very few slow end-to-end tests.
Tool Calling
Giving a model a set of typed function definitions it can request to invoke, with the application executing the call and returning the result.
Webhook
An HTTP callback from a provider to a consumer-supplied URL when an event occurs, replacing polling with push.
gRPC
A contract-first RPC framework using Protocol Buffers over HTTP/2, with generated clients and servers and first-class streaming.
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
You are designing APIs for a platform with a web app, a mobile app, internal service-to-service traffic and third-party partners. What do you expose, and where?
What the interviewer is testing Whether you choose per constraint or adopt one technology as an identity. The wrong answers here are all defensible sounding and
Partner & B2B Integration
External contracts, onboarding, sandboxes and long deprecation windows.
API & Integration
General material on integrating systems through contracts.
Enterprise Integration
Estate-wide integration strategy, standards and shared infrastructure.
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.
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.
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.
Contract Testing
Verifying what consumers actually rely on, without a shared environment.
GraphQL
Client-specified queries, N+1 resolution and query-cost control.
Idempotency Keys
Client-generated keys stored atomically with the operation they guard.
Message Formats
JSON, Protobuf, Avro — schema evolution and payload economics.
Pagination & Filtering
Offset versus cursor, stable ordering and unbounded result sets.
REST Design
Resources, uniform methods, status codes and statelessness.
Rate Limiting
Algorithms, shared counters, and signalling rejection properly.
Schema Registry
Enforcing compatibility on events the way CI enforces it on code.
Webhooks
Push callbacks, signature verification, ordering and at-least-once delivery.
gRPC APIs
Contract-first RPC, generated clients and protobuf compatibility rules.