Monitoring Apparatus Throughput Expansion Without Downtime
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing monitoring systems face challenges in expanding throughput quickly without downtime, especially when both containerized and non-containerized components are involved, as current technologies are not suited for simultaneous scaling and require time to adjust database throughput.
Innovation Solution
A monitoring system with a containerized component and a non-containerized database that includes an identification unit to detect throughput issues, a throughput expansion unit to restrict and expand data flow, and a restoration unit to reflect changes, allowing for continuous monitoring and expansion without downtime.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If database throughput is expanded without downtime, then system availability is maintained, but expansion time is required and complexity increases
Solution Approach 1:
The patent applies preliminary action by creating a read-only replica database before the original database becomes unavailable. This replica is prepared in advance with the same schema and initial data, so when throughput expansion is needed, the system can immediately switch to using the replica while the original database is being expanded, thereby maintaining continuous availability without downtime.
Solution Approach 2:
The patent segments the database system into two independent parts: the original database and the read-only replica database. This segmentation allows them to operate independently - the original database can be expanded or maintained while the replica handles read operations, enabling throughput expansion without affecting overall system availability.
2Productivity
If containerized applications are used for monitoring, then scalability is improved, but compatibility with non-containerized databases is reduced
Solution Approach 1:
The patent applies universality by making the monitoring system work with both containerized applications and non-containerized databases. The system uses standardized data collection interfaces that can gather metrics from containerized monitoring targets while storing data in traditional non-containerized databases, allowing the monitoring system to serve multiple purposes and environments simultaneously.
Solution Approach 2:
The patent introduces an intermediary layer - the monitoring system itself - that bridges containerized applications and non-containerized databases. This intermediary collects data from containerized sources using standard protocols and interfaces with non-containerized databases through database connection pools, enabling communication between the two different technological environments without requiring either side to change fundamentally.
3Productivity
If data collection is restricted during database expansion, then expansion performance is improved, but monitoring data loss occurs
Solution Approach 1:
The patent applies copying by creating a complete copy of the database (the read-only replica) that can be used during expansion operations. While the original database is being expanded with restricted data collection, the replica continues to serve read operations and can be synchronized with any new data, preventing data loss while maintaining expansion performance.
Solution Approach 2:
The patent implements discarding and recovering by temporarily redirecting data collection away from the original database during expansion (discarding the original write path) and then recovering by synchronizing this data to the replica or resuming writes after expansion completes. This ensures no monitoring data is permanently lost during the expansion process.
Data Source
AI summary
A monitoring system according to one embodiment is a monitoring device including: a first component implemented by a containerized application; and a second component implemented by a non-containerized application, wherein the monitoring device further includes: an identification unit configured to identify, based on information on a processing status of the first component and a processing status of the second component, a component which is running out of throughput among the first and second components; a first throughput expansion unit configured to restrict data flowing to the second component and expand throughput of the second component in a case where the second component is identified as running out of throughput; and a restoration unit configured to cancel data restriction for the second component and reflect data occurring during the throughput expansion of the second component in a case where the throughput of the second component is expanded.