Distributed Component-Based Application Deployment Architecture
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Monolithic software applications face challenges with reduced agility, inability to accommodate continuous delivery and deployment, and inefficient scalability due to their single-unit packaging, which requires system downtime and wastes resources when scaling.
Innovation Solution
A distributed component-based architecture is deployed using microservices, where applications are decomposed into smaller, loosely-coupled services, each with a base component that operates independently and communicates through a box-and-port pattern, enabling asynchronous processing and efficient resource utilization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If monolithic application packaging is used, then deployment is straightforward, but agility is reduced and continuous delivery is prevented
Solution Approach 1:
The patent divides a monolithic application into multiple independent microservices that can be deployed separately. Each microservice is packaged individually in EAR/WAR/JAR formats and deployed to the application server independently, enabling continuous delivery and improved agility while maintaining standardized deployment processes.
2Ease of manufacture
If monolithic application packaging is used, then deployment is straightforward, but continuous delivery and deployment are prevented
Solution Approach 1:
The application is segmented into independent microservices that can be developed, tested, and deployed continuously without affecting other services. The standardized packaging formats (EAR/WAR/JAR) enable automated build and deployment pipelines, facilitating continuous delivery while maintaining deployment simplicity through consistent packaging standards.
3Productivity
If horizontal scaling of monolithic application is performed, then demand accommodation is achieved, but resource waste occurs due to duplication of less-in-demand services
Solution Approach 1:
The monolithic application is segmented into independent microservices, allowing selective scaling of only those services that experience high demand. Each microservice can be replicated and scaled independently based on its specific resource requirements, eliminating the resource waste associated with scaling entire monolithic applications including low-demand services.
4Adaptability or versatility
If one component in monolithic application is changed, then component updates are possible, but entire application must be repackaged causing system downtime
Solution Approach 1:
The application is divided into independent microservices packaged in standardized formats (EAR/WAR/JAR). When a component needs updating, only the affected microservice package is rebuilt and redeployed, while other services continue running. This eliminates the need to repackage the entire application and prevents system downtime during component updates.
5Adaptability or versatility
If microservice architecture is used, then modularity and independent deployment are improved, but system complexity increases
Solution Approach 1:
The patent establishes a universal standardized packaging format (EAR/WAR/JAR) that all microservices adhere to, providing a common interface and deployment mechanism. This universality simplifies the management of multiple microservices, reducing the complexity that would otherwise arise from heterogeneous service structures while maintaining high modularity and independent deployment capabilities.
Data Source
AI summary
A system and method for deploying a distributed component-based application is disclosed. The system may include a plurality of uniform base components. Each base component of the plurality of uniform base components may host a respective service component, and may include an input port, an output port, a service port, an error, log, and exception port, a monitoring port, and a control port. A first base component may process event messages asynchronously with a second base component and a third base component. The system and method may also support auto-scalability of each base component.