Microservice Web Deployment for Granular Scaling and Cache Preservation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing web service deployment methods are inefficient, rigid, and fail to leverage operating system resources, leading to errors, cache loss, and inability to scale at a granular level without special-purpose code.
Innovation Solution
Implementing web services as discrete microservices on individually addressable nodes, using a common communication protocol and framework to facilitate scalability, efficiency, uniformity, and deployability, allowing dynamic resource allocation and caching.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If traditional web service deployment methods are used, then existing applications can be maintained, but deployment efficiency is poor and cache is lost during upgrades
Solution Approach 1:
The patent divides the web service into discrete microservices that can be independently deployed and upgraded. Each microservice is a separate unit that can be modified without affecting other services, allowing incremental deployments that preserve the cache of unaffected services while updating only the specific microservice being modified.
Solution Approach 2:
The patent implements dynamic deployment capabilities where microservices can be updated, added, or removed at runtime without requiring application restarts. This dynamic approach allows the system to maintain cache integrity during upgrades by selectively deploying only affected microservices while keeping other services and their caches intact.
2Adaptability or versatility
If monolithic software systems are used, then system simplicity is maintained, but scalability at granular level is not possible without special-purpose code
Solution Approach 1:
The patent segments the monolithic application into multiple independent microservices, each capable of being scaled independently. This segmentation enables granular scalability where only specific microservices needing additional capacity are replicated, rather than scaling the entire monolithic system.
Solution Approach 2:
The patent employs a universal framework that provides common functionality across all microservices, including standardized deployment mechanisms, communication protocols, and caching strategies. This universal framework eliminates the need for special-purpose code for each microservice while maintaining the ability to scale granularly.
3Ease of manufacture
If recompilation is used for reuse, then existing functionality can be preserved, but extraction difficulty increases and compile-time compatibility is required
Solution Approach 1:
The patent extracts functionality into separate microservices that can be independently developed and deployed. This segmentation allows specific functions to be extracted and reused without requiring compilation of the entire application, as each microservice is a self-contained unit that can be modified independently.
Solution Approach 2:
The patent uses microservice templates and frameworks that can be copied and instantiated multiple times. Existing functionality is preserved through reusable microservice components that can be deployed without recompilation, utilizing interpretation or runtime execution instead of compile-time binding.
4Reliability
If integrated caching strategies are built into software stacks, then caching functionality is available, but flexibility and adaptability are reduced
Solution Approach 1:
The patent introduces a caching framework that acts as an intermediary layer between microservices and data stores. This framework provides standardized caching mechanisms while maintaining flexibility, allowing developers to configure caching strategies dynamically without modifying the core software stack.
Solution Approach 2:
The patent implements dynamic caching configurations where caching parameters such as expiration times, validity rules, and storage locations can be changed at runtime without requiring code modifications. This dynamic approach allows the system to adapt caching strategies to changing requirements while maintaining reliable caching functionality.
Data Source
AI summary
A system for providing a web service on a network of addressable nodes, said web service comprising a plurality of discrete, individually-addressable microservices, said system comprising: (a) at least one load balancer configured for routing a request from a node for a microservice to one of a plurality of virtual addresses, each virtual address corresponding to a unique microservice, and (b) one or more physical nodes associated with each virtual address, each physical node comprising one or more microservices, each microservice comprising a microservice-specific module for executing a particular function, said microservice-specific module linked to an interface for communicating over said network, each microservice being one of a plurality of individually-addressable microservices constituting a web service.