Video Content Pushing via Standby System Activation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing disaster recovery solutions for video recommendation services are not robust enough, as they depend on services like item_list or redis, and fail when these dependent services fail, leading to inability to push video content to users.
Innovation Solution
Activating a standby disaster recovery system when the primary system fails, and using historical video content stored in a middleware to continue video playback, eliminating dependence on other services and ensuring continued video content delivery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the disaster recovery solution stores popular videos through item_list or redis and pushes videos by accessing these services, then the video pushing function can be implemented, but when the depended services or basic services fail, the videos cannot be pushed, making the disaster recovery solution not robust enough
Solution Approach 1:
The patent creates a local copy of video content in the disaster recovery system instead of relying on external services like item_list or redis. When services fail, the local copy ensures video pushing continues without interruption, eliminating the single point of failure while maintaining the video pushing functionality.
Solution Approach 2:
The patent pre-stores video content and metadata locally in the disaster recovery system before service failures occur. This beforehand preparation ensures that when external services fail, the system immediately has the necessary data available without needing to access failed external services, thus cushioning against service failures.
2Reliability
If the disaster recovery system depends on item_list or redis service for video pushing, then the system can utilize existing service infrastructure, but when these services fail, the entire disaster recovery mechanism fails, reducing system stability
Solution Approach 1:
The patent extracts the critical video content and metadata from external services (item_list, redis) and stores them locally within the disaster recovery system. This extraction eliminates the dependency on external services for video pushing operations, allowing the system to function independently when external services fail while maintaining stability.
3Ease of operation
If the system uses external services like consul for basic operations, then the system can leverage centralized service discovery and management, but when these basic services fail, the video pushing capability is lost, indicating insufficient disaster recovery robustness
Solution Approach 1:
The patent segments the video pushing functionality from the external service dependencies by implementing a self-contained disaster recovery system with local video content storage. This segmentation allows the video pushing core function to operate independently of external service management systems like consul, ensuring operational continuity even when service management fails.
Data Source
AI summary
Disclosed are a video content push method and apparatus, the method comprising: when a primary disaster recovery system of a video recommendation service fails, activating a standby disaster recovery system; receiving a video access request sent by an application client, and invoking first historical video content stored in middleware and obtained from historical video recommendations of the video recommendation service according to a preset proportion; pushing the first historical video content to the application client for playback. The method removes the dependence of recovery on other services, so that a recovery solution is more robust, thereby increasing the stability of video content pushing.