Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
23 results for “Batch Orchestration”
DAG Dependency
The declared edge stating that one task must not start until another has succeeded, and the difference between that and merely running later.
Failover Orchestration
The sequence of detection, decision, promotion and traffic redirection that moves service from a failed component to a healthy one.
Pipeline Orchestration
Coordinating the execution of data tasks by dependency rather than by clock, with retries, backfill and observability built in.
File-Based Integration
Exchanging data as files on a schedule via SFTP or shared storage — dated, still ubiquitous, and workable when its failure modes are handled explicitly.
Freshness Requirement
How stale data may be before the decision it supports degrades — the only question that justifies streaming over batch.
Health Check
An endpoint the platform polls to decide whether an instance should be restarted or should receive traffic — two different questions needing two different checks.
Kubernetes
A container orchestrator that continuously reconciles the running state of a cluster towards a declared desired state.
Merge Upsert
Applying a batch of changes to a target by matching on a key and inserting, updating or deleting per row, which is expensive and frequently avoidable.
Migration Wave
A batch of applications migrated together, sequenced so that dependencies move in a workable order and each wave delivers learning for the next.
Process Manager
A component that owns the state and sequencing of a multi-step business process, deciding what happens next in response to events.
Saga Orchestrator
A component that explicitly drives a saga's steps and compensations, holding the flow in one place rather than distributing it across event subscriptions.
A CDC pipeline feeding your warehouse falls three hours behind during a source system's batch job, and the source's transaction log retention is 24 hours. What is the risk and what do you change?
The immediate risk Lag consumes the retention window. At three hours behind against a 24 hour retention, you have 21 hours of margin. If the consumer stops enti
A business sponsor asks for a real-time data platform because "the competition has one". Reporting is currently a nightly batch that lands at 06:00 and nobody has complained. How do you handle this?
Do not answer the technology question "Real time platform" is a solution, and it has arrived without a problem attached. Answering it directly leads either to a
A core mainframe system with no API supports nightly batch file exchange only. The business needs near-real-time order status. Design the integration.
Establish the real constraint "No API" usually means no API the mainframe team will build on your timeline . Find out what exists: message queue interfaces, dat
A streaming aggregation reports lower totals than the batch job it replaced. Both read the same source. What is likely happening?
The likely cause: late events dropped past the watermark The batch job reads a completed day and sees everything, including records that arrived hours after the
One customer's batch job saturates a shared service and degrades everyone. Rate limiting them fixes it, until the next customer does the same. What is the structural answer?
Why per customer rate limits keep failing A static limit is set from what that customer was doing, not from what the service can serve. It is reactive — you dis
Your API gateway configuration has grown to 8,000 lines with request transformations and cross-service orchestration. Changes require a platform team ticket and take two weeks. How do you fix this?
Name the failure The gateway has become a distributed monolith — shared, centrally owned, untestable in isolation, and on the critical path of every team's deli
Your streaming aggregate reports 2% lower daily revenue than the batch reconciliation. Both are "correct". Explain what is happening and how you resolve it.
The likely cause: silently dropped late data The streaming job windows by event time and closes each window when the watermark passes. Records arriving after th
Batch Orchestration
DAGs, dependencies, retries, and the difference between a schedule and an orchestration.
Orchestration vs Choreography
A coordinator that knows the flow, or services that react to events.
Streaming vs Batch
The freshness requirement that actually justifies streaming, and the cost of assuming one.
Mainframe Modernization
Batch windows, COBOL, and the risk profile of core banking systems.