Application flexible assembly system based on service component

Abstract

The invention relates to an application flexible assembly system based on a service component, and belongs to the technical field of computers. The application flexible assembly system comprises a basic platform, a service assembly, a service bus and an application framework. The invention provides a one-stop application assembly capability taking a business service component as a core. Each business service component is developed and packaged on the business level based on a unified data standard, a communication protocol and a style and style to serve as a minimum business and operation unit of application assembly. And then, an application system developer can select and assemble the business service components through the application framework to form an application system meeting various business scenes. According to the architecture and the technology, the difficulty that business codes need to be developed from zero every time in a traditional development mode is solved, a batch of atomic-scale business service components are provided on the business level, the ability of business functions to take urgent use is formed, and the generation efficiency of an application system is improved.

Description

Technical Field

[0001] This invention belongs to the field of computer technology, specifically relating to a flexible application assembly system based on service components. Background Technology

[0002] Today, computer software has become an important part of information technology development. Especially in some key areas, developing computer software has become an important task in order to meet people's work and life requirements and improve work efficiency.

[0003] However, with the development of business needs and the increasing number of business application systems, application development costs are rising, and there is a significant amount of repetitive development work. To improve application development speed and reduce costs, the application system is broken down into independent service components that meet the needs of smaller business operations. These components are then flexibly assembled using a unified upper-layer application framework to form an application system that meets multiple business scenarios.

[0004] Currently, component-based software development has become a widely used application software development approach, effectively reducing development difficulty and costs. However, most components used in current software development are general-purpose technical components that have only been encapsulated at the technical level and lack business significance, thus not reducing the amount of development required to meet business needs. Therefore, encapsulating components at the business level to form independent service components that meet specific business requirements, and then flexibly assembling these service components to create applications that meet multiple business scenarios, has become a more convenient application development technology.

[0005] To address diverse business needs, different service components require development. To ensure flexible assembly between these components, this invention establishes unified data standards, communication protocols, and style standards as development criteria for service components, and proposes an architecture of "one framework, one bus, one platform, and multiple components." This architecture aims to achieve unified management, data interoperability, and flexible assembly of service components. Specifically, the service bus provides unified management of service components, the basic platform provides fundamental functions such as unified authentication, unified permissions, unified users, and data interoperability between components, and the application framework provides flexible assembly capabilities for service components. Summary of the Invention (a) Technical problems to be solved The technical problem this invention aims to solve is how to provide a flexible application assembly system based on service components to address the difficulty of developing business code from scratch every time in the traditional development model.

[0006] (II) Technical Solution To address the aforementioned technical problems, this invention proposes a flexible application assembly system based on service components, which includes: a basic platform, service components, a service bus, and an application framework. The basic platform includes modules such as unified user service, unified messaging service, unified file service, and unified data storage and caching service. The unified user service provides basic user query, user synchronization, user authentication, and user authorization functions for upper-layer service components, service bus, and application framework. The unified messaging service provides asynchronous message communication functions for upper-layer service components, service bus, and application framework. The unified file service provides unified file upload, storage, query, and download functions for upper-layer service components, service bus, and application framework. The unified data storage and caching service provides data storage, query, and caching functions for upper-layer service components, service bus, and application framework. Service components rely on underlying user, message, file, data storage, and caching infrastructure services. Component developers develop and encapsulate these components at the business level based on unified data standards, communication protocols, and style guidelines, forming independent business service components that meet the needs of small businesses. When assembling applications, these business service components serve as the smallest business and operational units. Application system developers select and drag these business service components within the application framework to create applications that meet multiple business scenarios. The service bus provides support for the registration and management of service components. All service components need to connect to the service bus according to the standard, complete the registration of service component instances and metadata, and be managed by the service bus throughout their entire lifecycle, including: registration, publication, review, delisting, and cancellation. Application Framework: This is the application assembly and management module of the entire architecture, providing full lifecycle management for application systems, including creation, assembly, review, release, delisting, deregistration, and access. The application framework is divided into two parts: the development end and the user end. The development end is the application development platform, aimed at application system developers, providing them with full-process management capabilities for application system creation, assembly, review, release, delisting, and deregistration. The user end is for application users, serving as the application access platform and entry point provided by the application framework. After logging into the application access platform, users can view and access all application systems within their authorized scope.

[0007] (III) Beneficial Effects This invention proposes a flexible application assembly system based on service components. Compared with existing technologies, this invention presents a flexible application assembly architecture design centered on business-oriented service components (i.e., business service components), featuring a "one framework, one bus, one platform, and multiple components" structure. This architecture mainly comprises four parts: application framework, service bus, service components, and basic platform. Compared to traditional software development based on technical components, this invention provides a one-stop application assembly capability centered on business service components. Each business service component is developed and encapsulated at the business level based on unified data standards, communication protocols, and style guidelines, serving as the smallest business and operational unit for application assembly. Application system developers can then select and assemble business service components through the application framework to form application systems that meet various business scenarios. This architecture and technology solve the difficulty of developing business code from scratch every time in traditional development models, providing a batch of atomic-level business service components at the business level, enabling readily available business functions and improving application system generation efficiency. Attached Figure Description

[0008] Figure 1 This is a diagram of the overall architecture of the present invention; Figure 2 This is a diagram of the service component lifecycle management model of the present invention; Figure 3 This is a flowchart of the service component information management process of the present invention; Figure 4 This is a diagram of the application system's full lifecycle management model according to the present invention; Figure 5 This is a diagram of the service component collaboration model of the present invention. Detailed Implementation

[0009] To make the objectives, contents, and advantages of the present invention clearer, the specific embodiments of the present invention will be described in further detail below with reference to the accompanying drawings and examples.

[0010] The purpose of this invention is to propose a flexible application assembly system based on service components. It aims to achieve flexible software assembly by using service components with unified data, communication, and style standards to meet the needs of small businesses, thereby forming an application system that meets multiple business scenarios.

[0011] 1. Overall Architecture Figure 1 This is a diagram of the overall architecture of the present invention, as shown below. Figure 1 As shown, the overall architecture consists of the following four parts: The foundational platform, serving as the core support for the entire architecture, primarily includes modules such as Unified User Service, Unified Messaging Service, Unified File Service, and Unified Data Storage and Caching Service. The Unified User Service provides basic user query, synchronization, authentication, and authorization functions for upper-layer service components, the service bus, and the application framework. The Unified Messaging Service provides asynchronous message communication capabilities for upper-layer service components, the service bus, and the application framework. The Unified File Service provides unified file upload, storage, query, and download functions for upper-layer service components, the service bus, and the application framework. The Unified Data Storage and Caching Service provides data storage, query, and caching functions for upper-layer service components, the service bus, and the application framework.

[0012] Service components are the core of the entire architecture, relying on underlying basic services such as user, message, file, data storage, and caching. Component developers create and encapsulate these components at the business level based on unified data standards, communication protocols, and style guidelines, forming independent business service components that meet specific business needs. During application assembly, these business service components serve as the smallest business and operational units. Application system developers can select and drag these components within the application framework to create applications that meet various business scenarios.

[0013] Service Bus: As the management module for service components in the entire architecture, it provides support for the registration and management of service components. All service components need to connect to the service bus according to standards, complete the registration of service component instances and metadata, and be managed by the service bus throughout their entire lifecycle, including: registration, publication, review, delisting, and cancellation.

[0014] The application framework is the application assembly and management module of the entire architecture. It provides full lifecycle management for application systems, including creation, assembly, review, release, delisting, deregistration, and access. The application framework is divided into two parts: the development end and the user end. The development end is the application development platform, aimed at application system developers, providing them with full-process management capabilities for application system creation, assembly, review, release, delisting, and deregistration. The user end is for application users, serving as the application access platform and entry point provided by the application framework. After logging into the application access platform, users can view and access all application systems within their authorized scope.

[0015] 2. Standardize service components Service components, as independent small business units, are typically developed and provided by various third-party service providers. Due to differences in their technology stacks, specifications, and development habits, the final service components often exhibit inconsistencies in data formats, communication protocols, and interface styles. This inconsistency necessitates compatibility development during application assembly to address the unique data or protocols of each service component, adding significant customization work. Moreover, this workload increases proportionally with the number of service components.

[0016] Therefore, establishing unified service component standards is key to flexible application architecture. Unified service component standards, serving as specifications to be followed during the development of each service component, include unified data standards, unified communication protocols, and unified style guidelines, resolving inconsistencies in data, protocols, and styles among different service components.

[0017] The unified data standard defines JSON as the input and output data format for service components. It also defines naming conventions for data fields, such as camelCase, English naming, and naming with business meaning. For output data, the data standard defines the basic hierarchical structure and basic fields. The basic data hierarchy is divided into two layers. The first layer is basic response data, including basic response codes, response descriptions, and response business data fields. It also defines the enumeration range of response codes, including code values ​​for success, failure, insufficient permissions, and non-existent account. The second layer is business data, defining the names and value types of some basic business fields, such as name, content, and description.

[0018] The unified communication protocol defines the data interoperability protocol and API call specifications between service components. The data interoperability protocol uses either HTTP or HTTPS. HTTP and HTTPS, as common application-layer communication protocols on the internet, effectively reduce the difficulty of interoperability between service components. The API calls are defined in a RESTful style, and the API paths use all-English names that reflect business logic.

[0019] A unified style defines the style of service component pages, including the overall layout and color scheme, font type and size, icons, etc. As fundamental elements of an application, consistent page styles ensure a unified overall style for the final application system.

[0020] 3. Service Component Lifecycle Management Model Service components are the core of the entire flexible application assembly system, serving as the smallest operable unit in the application assembly process. Simultaneously, within the application system, service components are also the smallest business unit, carrying the application's business logic. Therefore, the management of service components is crucial for upper-layer application assembly.

[0021] For service components, this invention constructs a complete service component lifecycle management model, such as... Figure 2 As shown, this model adopts a centralized management mode of "1+N" (1 service bus + N service components). With the service bus as the core, it manages the entire lifecycle of the N service components, including service component standards, service component instances, and service component information. The service bus, as a unified service component management platform, is internally divided into three modules: a service component registry, a service component open platform, and a service component management platform. The service component registry provides real-time service component instance registration and management functions. The service component open platform is for application developers, providing functions such as querying, accessing, and searching for published components, and providing relevant component standards, including component development standards, component interface standards, and component usage standards. The service component management platform is for component administrators, providing full lifecycle management for third-party provided service components from creation to publication and deregistration.

[0022] Furthermore, from the perspective of the entire service component management process, this model can be divided into three stages. The first stage is the construction of service components. Each third-party service provider develops and implements service components according to service component standards to encapsulate their own business logic and ultimately provides service component deployment software for deployment. The second stage is the registration and management of service component instances. After successful deployment, each service component automatically registers its deployment instance information with the service bus, which then manages and maintains all service instances uniformly, monitoring their operational status in real time. The third stage is service component information management, providing end-to-end management from creation to release and deregistration. This includes component information registration, component release, component review, component delisting, component deregistration, and component version management, as detailed in the following process: Figure 3 As shown.

[0023] 4. Application System Full Lifecycle Management Model The application system is the value deliverable of the entire flexible application assembly system and the final result of application assembly. Regarding the assembly and generation of application systems, this invention constructs a complete application system lifecycle management model, such as... Figure 4 As shown, this model, with the application framework at its core and service bus and service components as its foundation, forms a dual-end capability ("developer end + user end"), providing application systems with full lifecycle management including creation, assembly, review, release, delisting, deregistration, and access.

[0024] The application framework's "dual-end" capability architecture mainly consists of one backend (i.e., the application framework backend service) and two platforms (i.e., the application development platform and the application access platform). The application framework backend service is primarily responsible for the management and maintenance of application system metadata, including data storage, data querying, data modification, and data flow. The externally provided API calls are uniformly defined in a RESTful style, using HTTP or HTTPS as the communication protocol and JSON as the data transmission format.

[0025] The application development platform is designed for application system developers, providing a development model centered on the application system, built upon service components, and utilizing flexible assembly. Its core capabilities are divided into two parts: the first is end-to-end application development management, and the second is application assembly based on service components. End-to-end application development management defines all stages involved in the application development process, including application system creation, assembly, review, release, delisting, and deregistration, achieving full-process control and ensuring the standardization of application development. The entire process is as follows: application system developers log in and access the application development platform, create an application system, fill in application information, and complete application development by dragging and dropping business service components. Then, the completed application system is submitted for review. After approval, it can be released, and the released application can also be delisted and deregistered.

[0026] Application assembly based on service components is the second step in the application development process and is also the module that truly supports the implementation of application development. During application design and development, the application assembly module provides users with various general application templates, each with a fixed structure, such as left-right or top-middle-bottom structures. The templates contain slot-like blank windows to support the arbitrary insertion and assembly of service components. Technically, the application development platform heavily relies on the underlying service bus and service components. It calls the service bus via HTTP or HTTPS interfaces through the application framework's backend service to obtain published service component data. The generated application system metadata exists in JSON format and is returned to the application framework's backend service via HTTP or HTTPS interfaces, finally being stored through the unified data storage service of the underlying platform.

[0027] The application access platform, geared towards end-users, serves as a centralized entry point for application access, providing capabilities such as application querying, application access, and application permission control. After logging into the platform, users can view and access all application systems within their authorized scope. Technically, the platform integrates with a unified user service via HTTP or HTTPS interfaces, enabling unified authentication between the platform and multiple applications. Furthermore, the platform queries published applications and their access permissions from the application development platform via API calls, returning the data in JSON format, which is then parsed and displayed.

[0028] 5. Service component collaboration model In the entire flexible application assembly system, service components are the smallest operational units and also the smallest business units. Flexible assembly of these independent service components, each meeting small business needs, can form application systems that satisfy multiple business scenarios. However, in some complex business scenarios, there are business collaborations between the multiple service components that make up the application. To break down the business barriers between service components and achieve business collaboration among multiple service components, this invention constructs a service component business collaboration model based on a unified service component standard, such as... Figure 5 As shown.

[0029] The service component collaboration model, centered on service components and based on a service bus, constructs a collaboration pattern of "synchronous invocation + asynchronous messaging." At the underlying level, a unified user service enables global user unification and authentication. In synchronous invocation mode, service components strongly depend on the service bus, requiring them to register with the service bus and generate a unique service name. When a service component calls the interface of another service component, it needs to query the relevant service component instance from the service bus using the service name and then send an HTTP or HTTPS request. In asynchronous messaging mode, each service component needs to interface with the unified messaging service, sending messages to the unified messaging service via HTTP or HTTPS interface calls. The unified messaging service then pushes the messages to a message queue for a specified topic, awaiting consumption by other service components. In this producer-subscribe approach, each service component generates messages for one or more topics and can also subscribe to messages for one or more topics.

[0030] Compared to existing technologies, this invention proposes a flexible application assembly architecture design centered on business-oriented service components (i.e., business service components), featuring a "one framework, one bus, one platform, and multiple components" structure. This architecture mainly comprises four parts: application framework, service bus, service components, and basic platform. Compared to traditional software development based on technical components, this invention provides a one-stop application assembly capability centered on business service components. Each business service component is developed and encapsulated at the business level based on unified data standards, communication protocols, and style guidelines, serving as the smallest business and operational unit for application assembly. Application system developers can then select and assemble business service components through the application framework to form application systems that meet various business scenarios. This architecture and technology solve the difficulty of developing business code from scratch every time in traditional development models, providing a batch of atomic-level business service components at the business level, enabling readily available business functions and improving application system generation efficiency.

[0031] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the technical principles of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A flexible application assembly system based on service components, characterized in that, The application's flexible assembly system includes: a basic platform, service components, a service bus, and an application framework; The basic platform includes modules such as unified user service, unified messaging service, unified file service, and unified data storage and caching service. The unified user service provides basic user query, user synchronization, user authentication, and user authorization functions for upper-layer service components, service bus, and application framework. The unified messaging service provides asynchronous message communication functions for upper-layer service components, service bus, and application framework. The unified file service provides unified file upload, storage, query, and download functions for upper-layer service components, service bus, and application framework. The unified data storage and caching service provides data storage, query, and caching functions for upper-layer service components, service bus, and application framework. Service components rely on underlying user, message, file, data storage, and caching infrastructure services. Component developers develop and encapsulate these components at the business level based on unified data standards, communication protocols, and style guidelines, forming independent business service components that meet the needs of small businesses. When assembling applications, these business service components serve as the smallest business and operational units. Application system developers select and drag these business service components within the application framework to create applications that meet multiple business scenarios. The service bus provides support for the registration and management of service components. All service components need to connect to the service bus according to the standard, complete the registration of service component instances and metadata, and be managed by the service bus throughout their entire lifecycle, including: registration, publication, review, delisting, and cancellation. Application Framework: This is the application assembly and management module of the entire architecture, providing full lifecycle management for application systems, including creation, assembly, review, release, delisting, deregistration, and access. The application framework is divided into two parts: the development end and the user end. The development end is the application development platform, aimed at application system developers, providing them with full-process management capabilities for application system creation, assembly, review, release, delisting, and deregistration. The user end is for application users, serving as the application access platform and entry point provided by the application framework. After logging into the application access platform, users can view and access all application systems within their authorized scope.

2. The application flexible assembly system based on service components as described in claim 1, characterized in that, The unified data standard defines JSON as the data format for both input and output of service components, and also defines the naming conventions for data fields. For output data, the data standard defines the basic hierarchical structure and basic fields. The basic hierarchical structure is divided into two layers: the first layer is the basic response data, including basic response codes, response descriptions, and response business data field information; it also defines the enumeration range of response codes, including codes for success, failure, insufficient permissions, and non-existent accounts; the second layer is the business data, defining the names and value types of some basic business fields.

3. The application flexible assembly system based on service components as described in claim 1, characterized in that, The unified communication protocol defines the data communication protocol and call interface specifications between service components. The data communication protocol adopts the HTTP or HTTPS protocol, the call interface adopts the RESTful style definition, and the interface path adopts all English names.

4. The application flexible assembly system based on service components as described in claim 1, characterized in that, A unified style defines the style of the service component pages, including: the overall layout and color scheme of the page, font type and size, and icons.

5. The application flexible assembly system based on service components as described in any one of claims 1-4, characterized in that, The full lifecycle management model adopts a "1+N" centralized management mode, namely 1 service bus + N service components. With the service bus as the core, it manages the entire lifecycle of N service components, including: service component standards, service component instances, and service component information. The service bus, as a unified service component management platform, is internally divided into three modules: a service component registry, a service component open platform, and a service component management platform. The service component registry provides real-time service component instance registration and management functions. The service component open platform, for application developers, provides query, access, and search functions for published components and provides relevant component standards, including: component development standards, component interface standards, and component usage standards. The service component management platform, for component administrators, provides full lifecycle management for third-party service components, from creation to publication and deregistration.

6. The application flexible assembly system based on service components as described in claim 5, characterized in that, The full lifecycle management model is divided into three stages. The first stage is the construction of service components, in which each third-party service provider develops and implements service components according to the service component standards to encapsulate its own business and finally provides service component deployment software for deployment. The second stage is the registration and management of service component instances. After each service component is successfully deployed, it will automatically register the deployment instance information with the service bus. The service bus will then manage and maintain all service instances in a unified manner and monitor the running status of all service instances in real time. The third stage is service component information management, which provides full-process management for service components from creation to release and deregistration. Specifically, it includes: component information registration, component release, component review, component removal, component deregistration, and component version management.

7. The application flexible assembly system based on service components as described in claim 6, characterized in that, The application framework's "dual-end" capability architecture includes one backend and two platforms: an application development platform and an application access platform. The application framework's backend service is responsible for the management and maintenance of application system metadata, including data storage, data query, data modification, and data flow. The external call interfaces are uniformly defined in a RESTful style, using HTTP or HTTPS as the communication protocol and JSON as the data transmission format.

8. The application flexible assembly system based on service components as described in claim 6, characterized in that, Application system developers log in and access the application development platform to create application systems, fill in application information, and complete application development by dragging and dropping business service components. Then, the completed application system is submitted for review. After approval, it can be released, and the released application can also be removed and deregistered. During the application design and development process, the application assembly module provides users with a variety of general application templates. Each template has a fixed structure and blank windows similar to slots to support the arbitrary plugging and unplugging and assembly of service components. The application development platform relies heavily on the underlying service bus and service components. It calls the service bus through the application framework backend service in the form of HTTP or HTTPS interface to obtain the data of the released service components. The metadata of the assembled application system exists in JSON format and is returned to the application framework backend service through HTTP or HTTPS interface. Finally, it is saved through the unified data storage service of the basic platform.

9. The application flexible assembly system based on service components as described in claim 8, characterized in that, The application access platform is geared towards end-users of applications and serves as a centralized entry point for application access, providing capabilities for application querying, application access, and application permission control. After logging into the application access platform, users can view and access all application systems within their authorized scope. In terms of technical implementation, the application access platform integrates with the unified user service through HTTP or HTTPS interfaces to achieve unified authentication between the platform and multiple applications. In addition, the application access platform queries the published applications and application access permissions from the application development platform through interface calls, returns the data in JSON format, and finally parses and displays it.

10. The application flexible assembly system based on service components as described in claim 9, characterized in that, The service component collaboration model is centered on service components and built upon a service bus, constructing a collaboration mode of "synchronous invocation + asynchronous messaging." At the underlying level, a unified user service is used to achieve global user unification and authentication. In synchronous invocation mode, service components strongly depend on the service bus, needing to register themselves with the service bus and generate a unique service name. When a service component calls the interface of another service component, it needs to query the relevant service component instance from the service bus using the service name and then send an HTTP or HTTPS request. In asynchronous messaging mode, each service component needs to interface with the unified messaging service, sending messages to the unified messaging service via HTTP or HTTPS interface calls. The unified messaging service then pushes the messages to the message queue of the specified topic, waiting for other service components to consume them. In this producer-subscribe approach, each service component generates messages for one or more topics and also subscribes to messages for one or more topics.

Images