Microhost Program Filesystem Service Discovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Microservice architectures present challenges in reducing the number of keystrokes required to bring systems online without introducing complexity or cost, particularly during integration with other microservices or monolithic architectures, and existing tools lack robustness in service discovery and file orchestration.
Innovation Solution
A microhost program that discovers microservices in a root directory using filesystem queries, allowing for efficient reorganization and elimination of the need for oversized router files or explicit dependency analysis, thereby reducing processing time and improving development speed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If microservice architectures are used to enable flexible development and deployment, then adaptability and development speed are improved, but device complexity and integration costs increase
Solution Approach 1:
The system enables self-service through automated service discovery where services automatically register themselves with the file system watcher, which then autonomously detects and propagates service location information across the distributed system without requiring manual configuration or coordination between services
Solution Approach 2:
The patent replaces manual service registration and dependency tracking mechanisms with an automated file system-based event-driven system. The file system watcher automatically detects changes in service locations and triggers appropriate actions, substituting complex manual orchestration with simple file system events
2Reliability
If explicit dependency analysis and coordination mechanisms are implemented between microservices, then service discovery reliability is improved, but processing time and development overhead increase
Solution Approach 1:
The file system watcher operates continuously in the background, constantly monitoring for service registration and location changes. This continuous operation eliminates the need for periodic service discovery requests or manual dependency analysis, maintaining up-to-date service information without interrupting the development workflow
Solution Approach 2:
Services automatically register themselves with the file system watcher during initialization, performing the service discovery setup in advance. This preliminary registration allows the system to have service location information ready before it is actually needed, eliminating on-demand discovery overhead
3Extent of automation
If network-based service communication is used as in Kubernetes and Docker Swarm, then service orchestration capability is improved, but communication overhead and deployment complexity increase
Solution Approach 1:
The file system acts as an intermediary between services, replacing complex network-based service meshes and orchestration layers. Service location and dependency information is stored as files in a shared file system, allowing services to discover and communicate with each other through simple file I/O operations rather than complex network protocols
Solution Approach 2:
Service location information and dependencies are copied into the file system as persistent records. This creates a tangible, versionable representation of service topology that can be inspected, backed up, and reproduced, replacing ephemeral network state with persistent file-based state
Data Source
AI summary
The present disclosure describes creating a cache of discovered directories in a filesystem stored on a data storage device wherein said cache of discovered directories describe packages that are semantically constructed as microservices, among numerous other aspects.