Campaign Management Server Failover System
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing Enterprise Marketing Management (EMM) solutions face disruptions and efficiency losses due to reliance on single servers and web-based authentication systems, which can lead to campaign management bottlenecks and productivity declines.
Innovation Solution
Implementing a system with two servers for each campaign-production environment, where one server acts as primary and the other as secondary, enabling synchronization of campaign contents and automatic failover and failback to ensure continuous campaign processing without sacrificing productivity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a single server is used for campaign management, then the system implementation is simple, but the campaign management is disrupted on server failure
Solution Approach 1:
The system is divided into multiple independent server nodes (primary server and secondary server) that can operate autonomously. Each server maintains the capability to handle campaign management independently, allowing the system to segment workload and failover to different nodes without complete system failure.
Solution Approach 2:
The system dynamically changes operational parameters by switching the active server role between primary and secondary servers based on failure conditions. This parameter change enables the system to adapt to failure scenarios while maintaining campaign management continuity.
2Reliability
If web-based authentication systems are implemented, then security is maintained, but productivity of campaign management declines due to bottlenecks
Solution Approach 1:
Authentication credentials and authorization tokens are pre-established and cached in the system before actual campaign management operations begin. This preliminary authentication action eliminates the need for repeated authentication checks during campaign execution, removing the bottleneck while maintaining security.
Solution Approach 2:
An intermediary authentication cache or token system is introduced between the web-based authentication system and the campaign management processes. This intermediary layer handles authentication requests efficiently by serving cached credentials, reducing the direct bottleneck impact on campaign management productivity.
Data Source
AI summary
Campaign-production management is performed for a plurality of campaigns on at least a primary server or a secondary server. The plurality of campaigns is processed on the primary server. The contents of the plurality of campaigns are synchronized between the primary server and the secondary server. On failure of the primary server, processing of the plurality of campaigns is transferred to the secondary server. Further, the failback of the processing of the campaigns is performed on the primary server.


