Transaction Authorization Server with Replicated Rule Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing transaction approval systems face challenges in meeting stringent timing requirements due to complex data processing and non-standardized data formats, leading to delays and inefficiencies in transaction approval processes.
Innovation Solution
A dual-server architecture is implemented, where a first server manages data and creates rules, and a second specialized server, the authorizer server, replicates relevant data for fast transaction approval, reducing data complexity and latency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a single server handles all transaction processing with full data storage and complex rule analysis, then comprehensive transaction review is achieved, but response time exceeds requirements and system becomes unstable
Solution Approach 1:
The system divides the single server into two specialized servers: a rule management server that stores comprehensive data and manages complex rules, and an authorizer server that handles real-time transaction approval. This segmentation allows each server to focus on specific functions, with the authorizer server making rapid approval decisions using replicated data while the rule management server maintains the complete rule set and data storage.
Solution Approach 2:
The authorizer server creates a partial replication of relevant data from the rule management server's data store. This copy contains only the essential transaction data needed for approval decisions, allowing the authorizer server to make real-time decisions without querying the full data store, thereby reducing latency while maintaining approval accuracy.
2Measurement precision
If complex rules and full data are processed in real-time, then accurate transaction approval is achieved, but data retrieval latency increases
Solution Approach 1:
The system extracts only the essential transaction data and rules needed for real-time approval decisions from the comprehensive data store. The authorizer server receives a streamlined subset of data that contains all necessary information for approval without the overhead of processing the entire data set, enabling fast and accurate decision-making.
Solution Approach 2:
The rule management server prepares and replicates relevant data and rules to the authorizer server in advance. This preliminary action ensures that when a transaction requires approval, the authorizer server already has the necessary data locally available, eliminating real-time data retrieval latency while maintaining the ability to apply complex rules accurately.
3Adaptability or versatility
If customized features and non-standardized data formats are added to existing systems, then transaction flexibility is improved, but data complexity and processing difficulty increase
Solution Approach 1:
The rule management server is designed to handle customized features and non-standardized data formats with specialized data processing capabilities. The authorizer server focuses on standard real-time approval operations using simplified data. This local quality differentiation allows the system to maintain high flexibility for customized transactions while keeping the real-time approval path simple and efficient.
Data Source
AI summary
A system for stable and streamlined transaction approval includes a rule management server and an authorizer server that operates independently of the rule management server. The rule management server is configured to receive a transaction rule associated with an account specified by a client entered through a portal generated by a graphical user interface. The server is further configured to identify data relevant to the transaction rule and transmit the transaction rule and the data identified to an authorizer server. The authorizer server is configured to receive transaction data related to a pending transaction of the credit card and apply the transaction rule to the transaction data and the data identified by the rule management server to determine whether to approve the pending transaction. The authorizer server operates independent of the rule management server and can be optimized to approve transactions quickly and operate in a stable condition.