Heterogeneous Garbage Collection via Service Type Components
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing garbage collection systems are not versatile enough to handle heterogeneous garbage types, limiting their applicability to scenarios where different types of garbage need to be collected.
Innovation Solution
A garbage collection method and apparatus that scans all service items, generates a service item list with target service types, determines corresponding collection components with unique garbage collection logics, and collects garbage using these components, allowing for the collection of heterogeneous garbage types by establishing and reusing collection components based on shared logics.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a unified garbage collection system is used for all service types, then the system structure is simple, but it cannot handle heterogeneous garbage types effectively
Solution Approach 1:
The patent implements a universal garbage collection framework that can handle multiple heterogeneous garbage types through a unified interface. The system defines a common Garbage interface that different garbage types (DatabaseGarbage, FileGarbage, PacketGarbage, etc.) implement, allowing the collection service to operate on various garbage types without requiring separate dedicated systems for each type.
Solution Approach 2:
The patent segments the garbage collection system into independent, modular components: different garbage types are divided into separate classes (DatabaseGarbage, FileGarbage, PacketGarbage, WorkflowGarbage), each with its own collection service. This segmentation allows each component to be developed, maintained, and scaled independently while maintaining overall system versatility.
2Reliability
If separate garbage collection systems are used for each garbage type, then each system is optimized for its specific type, but the overall system complexity increases
Solution Approach 1:
The patent merges multiple specialized garbage collection systems into a unified collection service framework. Different garbage types (database, file, packet, workflow) are collected by a single GarbageCollectionService that dispatches to appropriate collection logics based on the garbage type, reducing the number of independent systems while maintaining specialized collection capabilities for each type.
Solution Approach 2:
The patent introduces a GarbageCollectionService as an intermediary layer between the garbage types and the collection logics. This service acts as a mediator that receives garbage collection requests, determines the appropriate garbage type, and invokes the corresponding collection logic, thereby coordinating multiple specialized collection operations through a single unified interface.
3Productivity
If garbage collection logics are duplicated across different collection components, then each component is self-sufficient, but resource utilization decreases
Solution Approach 1:
The patent creates universal collection logics that can handle multiple garbage types through polymorphism. The GarbageCollection interface and its implementations are designed to be type-agnostic, allowing the same collection logic structure to operate on different garbage types (database, file, packet, workflow) without duplication, thereby improving resource utilization while maintaining versatility.
4Adaptability or versatility
If the garbage collection system is highly specialized for specific garbage types, then collection efficiency is high, but adaptability to new garbage types is poor
Solution Approach 1:
The patent uses parameter-based polymorphism where the garbage type is determined by parameters (such as service type identifiers) rather than hard-coded structures. The GarbageCollectionService can dynamically adjust its behavior based on the garbage type parameter, allowing it to maintain high collection efficiency for known types while easily adapting to new garbage types by simply registering new implementations that follow the same interface contract.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The present invention provides a garbage collection method and apparatus, comprising obtaining target service types comprised in all service items; determining target collection components corresponding to each of the target service types; and collecting garbage for the corresponding target service types by using each of the target collection components. In the present invention, collection components are established by using the service type as granularity, and different collection components are established to correspond to different service types. Performing garbage collection based on these components can flexibly expand the service types, thereby achieving the collection of heterogeneous service types with good versatility.