Custom Publisher Integration via Configuration as Code
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems face challenges in integrating new or custom publisher systems for merchant data distribution due to the need for hard-coded integrations and customized code, creating a technological barrier for efficient data delivery to publisher systems.
Innovation Solution
A custom publisher integration system that uses a configuration as code (CaC) file to define custom integration properties, enabling low-code environment setup and transformation of data streams from a merchant system to match the schema required by each publisher system, allowing for quick and efficient integration of custom publisher systems without lengthy development cycles.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If hard-coded integrations are used to deliver data to publisher systems, then data delivery reliability is improved, but integration complexity and time increase significantly
Solution Approach 1:
The patent introduces an intermediate system that acts as a mediator between the merchant system and publisher systems. This intermediate system provides standardized integration interfaces and data transformation capabilities, eliminating the need for hard-coded direct integrations between each merchant system and publisher system. The intermediary handles data formatting, validation, and routing, thereby maintaining data delivery reliability while significantly reducing integration complexity.
Solution Approach 2:
The intermediate system is designed with universal functionality to serve multiple publisher systems through a single integration point. It provides common data transformation, validation, and delivery mechanisms that work across different publisher platforms, reducing the need for customized code for each publisher and simplifying the overall integration process.
2Adaptability or versatility
If custom code is written for each publisher integration, then integration adaptability is improved, but development time and cost increase
Solution Approach 1:
The system employs dynamic configuration files that allow integration parameters, data mappings, and publisher-specific settings to be modified without changing the underlying code. This dynamic approach enables the system to adapt to different publisher requirements through configuration rather than development, maintaining integration adaptability while eliminating lengthy development cycles for each new publisher.
Solution Approach 2:
The patent utilizes parameter-based configuration where publisher-specific requirements are defined through configurable parameters in configuration files rather than hard-coded logic. By changing parameters in the configuration files, the system can adapt to different publishers' data formats, schemas, and delivery requirements without requiring custom code development, thereby reducing development time while maintaining adaptability.
3Productivity
If standardized integration interfaces are implemented, then integration speed is improved, but flexibility for custom publisher requirements decreases
Solution Approach 1:
The integration architecture is segmented into standardized interface layers and configurable parameter layers. The standardized interfaces provide fast, consistent data exchange protocols, while the configurable parameters allow customization for specific publisher requirements. This segmentation enables the system to maintain high integration speed through standardized processes while preserving flexibility through configurable parameters that can be adjusted without affecting the core integration mechanism.
Data Source
AI summary
A system and method to identify a first data stream from a data graph associated with a merchant system. A configuration file associated with a publisher system to receive data associated with the merchant system is identified. Based on a configuration file associated with the publisher system, a second data stream is generated which includes the data associated with the merchant system. The second data stream is transmitted to the publisher system.