Database Job Registration for Print Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing cloud print services face challenges in efficiently managing print jobs across multiple databases, particularly in ensuring continuous job processing without increasing processing load, especially when replication delays occur between master and slave databases.
Innovation Solution
An information processing technique that registers job information in a first database and asynchronously in a second database, allowing for job execution based on search results from the second database, even if the job information is not immediately available, by prioritizing unprocessed jobs and handling replication delays to prevent processing interruptions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If asynchronous replication is used between master and slave databases, then the response speed of data update process is improved, but a time delay occurs in mirroring completion causing job information to be unavailable from slave DB
Solution Approach 1:
The system performs preliminary registration of job information in the master database before the slave database completes mirroring. The print management server can immediately process job registration requests using the master database, without waiting for slave database synchronization, thus maintaining high response speed while ensuring data availability through the master database backup.
2Stability of the object's composition
If synchronous replication is used between master and slave databases, then data consistency is ensured, but the response speed of data update process decreases
Solution Approach 1:
The system segments the database replication process into asynchronous operations. The master database handles immediate job registration and data updates independently, while slave databases replicate data in the background without blocking the main processing flow. This segmentation allows the system to maintain data consistency across databases while preserving fast response speeds for job processing.
3Productivity
If job information is always searched from the second database, then load balancing is achieved, but processing interruptions occur when replication delay happens
Solution Approach 1:
The system introduces the master database as an intermediary backup source. When the slave database experiences replication delays or cannot provide job information, the print management server automatically switches to search the master database for job information. This intermediary mechanism ensures continuous job processing while maintaining load balancing benefits from the primary slave database approach.
4Device complexity
If a single database is used for job management, then device complexity is reduced, but the access load on the database increases
Solution Approach 1:
The system segments the database workload by deploying multiple databases (master and slave) to handle different aspects of job management. The master database handles immediate job registration and control functions, while slave databases handle job information storage and retrieval. This segmentation distributes the access load across multiple database instances while maintaining relatively simple database configurations and management procedures.
Data Source
AI summary
In a case where an execution request for a job to be executed by an external device is received, job information of the job is registered in a first database. A second database is searched for job information of a job for the external device which executes the job. Based on the found job information, predetermined processing is executed on a job corresponding to the job information. In a case where job information is searched for in accordance with registration of a job and at least the job information is not found, predetermined processing is executed, based on the registered job information held in an information processing apparatus, on a job corresponding to the job information.