LLI Event Routing With Document Database Parallel Processing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing sourcing systems struggle to process large line item (LLI) events efficiently, as they exceed the 30-second data processing limit and are not integrated with existing relational databases, limiting reporting and analysis capabilities.
Innovation Solution
A scalable solution that reroutes LLI event processing to a specialized content service using a document database, enabling parallel processing and concurrent validation of large data sets, and integrating with a microservice-based stack for faster data handling.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If LLI events are processed using existing sourcing systems with relational databases, then data processing can be performed, but the processing time exceeds the 30-second service level agreement
Solution Approach 1:
The system segments LLI event processing into separate microservices that can operate independently. The content service specifically handles LLI events with large data sets, while other services handle standard events, allowing parallel processing and preventing bottlenecks that would violate the 30-second service level agreement.
Solution Approach 2:
The patent introduces a message queue as an intermediary between event sources and processing services. Events are published to the message queue and processed asynchronously by available services, decoupling the submission of LLI events from their processing and enabling faster response times while maintaining reliability.
2Productivity
If LLI events are handled separately via spreadsheet input, then large data sets can be processed, but reporting and analysis features are limited due to separate database storage
Solution Approach 1:
The patent merges LLI event data storage with the main event database by implementing a unified event data model. Both standard events and LLI events are stored in the same database structure, enabling consistent reporting and analysis capabilities across all event types while maintaining the ability to handle large data sets efficiently.
Solution Approach 2:
The content service is designed with multi-functionality, handling not only LLI event processing but also serving as a universal event processing capability that can be invoked by various sources including user interfaces, integrations, and message queues, thereby providing both high productivity and broad adaptability.
3Ease of operation
If the system processes standard-size events with fewer than 2000 line items, then processing remains fast and integrated, but the system cannot efficiently handle LLI events with over 2000 line items
Solution Approach 1:
The system implements dynamic routing that automatically determines whether to process an event using the standard workflow or the specialized LLI content service based on the event's characteristics. This dynamic approach allows the system to maintain simple integrated processing for standard events while scaling to handle large events efficiently, optimizing both ease of operation and productivity.
Data Source
AI summary
In an example embodiment, a scalable solution is provided that identifies sourcing events that are large line item events and reroutes requests for operations related to such events to a specialized content service. The specialized content service authenticates the requests and causes data pertaining to the large line item events to be stored in and/or retrieved from a document database for LLI event processing. The result is that operations for LLI events are able to be processed much faster than in prior art solutions.