Serverless Batch Orchestration for Cross-System Data Reconciliation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Integrating disparate software systems for efficient routine batch processing is difficult and resource-intensive, particularly in enterprise computing environments.

Innovation Solution

A serverless batch processing system utilizing an event bus, workflow orchestration service, and containerized applications in an on-demand cloud computing environment to manage communication and reconciliation between programs, ensuring ordered execution and error handling.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional batch processing is used to integrate disparate software systems, then data integration can be achieved, but the process is difficult and time-consuming

Engineering Contradiction:

Improvebatch processing efficiencyVSAvoidintegration time

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The batch processing workflow is segmented into multiple independent containerized applications, each responsible for a specific integration task. This allows parallel execution of different integration operations, reducing overall processing time while maintaining coordinated data flow between systems.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

An event bus serves as an intermediary component that coordinates communication between disparate software systems. It enables reliable data exchange and triggers appropriate workflow steps without requiring direct point-to-point connections between all systems, simplifying integration complexity.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Productivity

If traditional batch processing is used for data integration, then processing can be performed, but resource consumption is high

Engineering Contradiction:

Improveprocessing capabilityVSAvoidresource overhead

Core Design Contradiction:

ProductivityVSUse of energy by moving object

Solution Approach 1:

The containerized applications automatically scale their resource consumption based on actual processing needs. Each application requests only the computing resources required for its current task, eliminating the need for over-provisioned fixed infrastructure and reducing overall resource overhead while maintaining processing capability.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The batch processing system dynamically adjusts resource allocation based on workflow progress and data volume. Resources are allocated to containerized applications as needed and released when complete, enabling efficient resource utilization that adapts to varying processing demands without wasting resources on idle capacity.

Inventive Principle:

Principle #15Dynamics

3Reliability

If complex integration workflows are implemented, then data reconciliation between systems is achieved, but system complexity increases

Engineering Contradiction:

Improvedata integrityVSAvoidworkflow management complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The event bus provides feedback mechanisms that track workflow execution status and data flow between systems. This enables automatic error detection, retry logic, and coordination without requiring complex manual orchestration, maintaining data integrity while simplifying workflow management through automated state tracking.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system manages integration complexity by parameterizing workflow configurations rather than hardcoding complex logic. Workflow steps, data transformations, and system connections are defined through configurable parameters that can be adjusted without changing underlying implementation logic, reducing maintenance complexity while ensuring data reconciliation.

Inventive Principle:

Principle #35Parameter changes

4Reliability

If manual monitoring of batch processing is performed, then control over processing is maintained, but operational overhead increases

Engineering Contradiction:

Improveprocessing controlVSAvoidoperational simplicity

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The containerized applications and event bus automatically monitor their own execution status, triggering appropriate responses without manual intervention. The system self-manages workflow progression, error handling, and resource allocation, eliminating operational overhead while maintaining reliable processing control through automated observability.

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS20260030047A1Serverless cloud computing

Publication Date: 2026.01.29 FMR CORP

AI summary

A computerized method is provided for batch processing in an on-demand cloud computing or serverless environment. Methods can include using a serverless event bus to trigger a workflow and a serverless workflow orchestration system to manage the workflow in a specified order among a number of containerized applications. In particular embodiments, serverless batch processing may be used to facilitate passage and reconciliation of data between disparate programs such as employee time entry, scheduling, and HR/payroll systems.