CN109783132B - Method and device for realizing system singleization and distribution - Google Patents

Abstract

The invention provides a method for realizing the singleization and the distribution of a adaptable system, which comprises the steps of disassembling service application into service sub-modules and realizing corresponding service logic by configuring metadata of the service sub-modules; each business sub-module interacts with the capability protocol, matches the corresponding capability unit through the interaction with the capability protocol, and completes the specific architecture function through the matched capability unit; performing contract-type dynamic matching on the execution capacity of each service sub-module related to the target release package according to the capacity integration specification to obtain each capacity unit meeting the requirement, and integrating each capacity unit through a capacity integration container; analyzing the content of each service submodule related in the target issuing package, searching and acquiring the issuing package of the corresponding service submodule, and combining and packaging the issuing packages into an application package. The invention can effectively solve the problem of smooth upgrade of the existing architecture capability and the problem of multi-versioning of service application caused by the change of the architecture capability.

Description

Method and device for realizing system singleization and distribution

Technical Field

The invention relates to the field of computers, in particular to a method and a device for realizing the system suitable for system singleization and distribution.

Background

With the continuous development of the technology and the promotion of the cloud business concept, more and more companies successively introduce the distributed cloud related technology in the aspect of business research and development, and although the distributed cloud generally has better performance, expansibility and stability, the complexity of system deployment, the requirement on the system operation and maintenance capacity level, the operation and maintenance difficulty and the like are also improved.

Due to different characteristics of various industries, in the existing partial industries, due to higher requirements on data security or requirements on fixed asset allocation or asset utilization, users usually want to run applications in their own machine room environment and refuse to use hosted or clouded SaaS versions; meanwhile, as the enterprises cannot be provided with technical talents with cloud operation and maintenance related capabilities, in this case, a better scheme is to provide a set of service system versions which are single and easy to deploy and operate and maintain.

Because many existing cloud technologies have strong intrusiveness or strong dependency on basic distributed capability, the cost in the framework replacement process is often high, for example, if upgrading from single-type to distributed-type is to be realized, framework adjustment and code change basically need to be involved, which is not only costly, but also seamless upgrading cannot be realized. Therefore, it is common to maintain two application versions with different architectures at the same time to support different scale usage scenarios, such as: the micro-service cloud version is used for supporting a large number of concurrent requests of a large number of users, and additionally, a set of single simple and easy version application is maintained and delivered to users which are unwilling to accept multi-tenant saas in small and medium scales, and the method directly causes application version branching, so that the difficulty and cost of maintenance management, bug revision, version iteration, commercialization and the like of multiple branch functions are improved. Meanwhile, in the related open source technology level, most of the current frameworks do not provide a complete and effective solution due to the limitation of the use surface.

Disclosure of Invention

One of the technical problems to be solved by the present invention is to provide a method for implementing system singleization and distribution, which can effectively solve the problem of smooth upgrade of the existing architecture capability and the problem of multi-versioning of service application caused by the change of the architecture capability.

The invention realizes one of the technical problems as follows: a realization method capable of adapting to system singleization and distribution, the method comprises the following steps:

step S1, disassembling the service application into each service sub-module according to the distributed standard, wherein each service sub-module has metadata configuration globally, and the metadata configuration of each service sub-module is used for realizing the corresponding service logic;

step S2, each business sub-module interacts with the ability protocol, matches the corresponding ability unit through the interaction with the ability protocol, and completes the specific architecture function through the matched ability unit;

step S3, performing contract-type dynamic matching on the execution capacity of each service sub-module related to the target release package according to the capacity integration specification to obtain each capacity unit meeting the requirement, and integrating each capacity unit through the capacity integration container;

step S4, analyzing the content of each service sub-module related in the target publishing packet, searching and obtaining the publishing packets of the corresponding service sub-modules, and combining and packaging the obtained publishing packets into an application packet.

Further, the metadata configuration contains metadata definitions of specific business function implementations, metadata definitions of capability protocols, or sdk interactions.

Further, the capability protocol is an abstract representation of the architectural capabilities, which describes information elements including metadata configuration, communication, request content elements, response specification, and exception branching for a particular architectural capability.

Further, the step S3 is specifically:

defining the integration mode and specification of each capacity unit to form a capacity integration specification, and providing complete integration realization for the capacity integration specification through the realization of a capacity integration container;

and for each service submodule related to the target publishing packet, searching metadata configuration of each service submodule in a deep traversal execution mode, dynamically matching each capacity unit meeting requirements according to capacity integration specifications and capacity protocol configuration of each service submodule, and integrating each matched capacity unit by using a capacity integration container.

Further, the step S3 further includes:

the capacity integration container realizes the forwarding of the requested flow to the corresponding capacity unit according to the capacity integration specification, thereby realizing the forward or reverse processing of the request from the capacity integration container to the capacity unit and then to the business submodule.

The second technical problem to be solved by the present invention is to provide an implementation device that is adaptable to system singleization and distribution, and the implementation device can effectively solve the problem of smooth upgrade of the existing architecture capability and the problem of multi-versioning of the service application caused by the change of the architecture capability.

The invention realizes the second technical problem in the following way: a can be suitable for the realization device of system singleization and distribution, the said realization device includes the business application disassembles the module, ability matching module, ability integration module and applies the package packing module;

the business application disassembling module is used for disassembling business application into each business sub-module according to a distributed standard, each business sub-module has metadata configuration globally, and corresponding business logic is realized by configuring the metadata of each business sub-module;

the capability matching module is used for interacting each service sub-module with a capability protocol, matching the service sub-modules with corresponding capability units through interaction with the capability protocol, and completing specific architecture functions through the matched capability units;

the capability integration module is used for carrying out contract type dynamic matching on the execution capability of each service sub-module related to the target release package according to the capability integration specification to obtain each capability unit meeting the requirement, and integrating each capability unit through the capability integration container;

and the application package packaging module is used for analyzing the content of each service submodule related in the target issuing package, searching and acquiring the issuing package of the corresponding service submodule, and combining and packaging the acquired issuing packages into the application package.

Further, the metadata configuration contains metadata definitions of specific business function implementations, metadata definitions of capability protocols, or sdk interactions.

Further, the capability protocol is an abstract representation of the architectural capabilities, which describes information elements including metadata configuration, communication, request content elements, response specification, and exception branching for a particular architectural capability.

Further, the capability integration module specifically includes:

defining the integration mode and specification of each capacity unit to form a capacity integration specification, and providing complete integration realization for the capacity integration specification through the realization of a capacity integration container;

and for each service submodule related to the target publishing packet, searching metadata configuration of each service submodule in a deep traversal execution mode, dynamically matching each capacity unit meeting requirements according to capacity integration specifications and capacity protocol configuration of each service submodule, and integrating each matched capacity unit by using a capacity integration container.

Further, the capability integration module further comprises:

the capacity integration container realizes the forwarding of the requested flow to the corresponding capacity unit according to the capacity integration specification, thereby realizing the forward or reverse processing of the request from the capacity integration container to the capacity unit and then to the business submodule.

The invention has the following advantages:

1. the method can perform abstract decoupling on business logic realization and architecture capability realization, not only can maintain independence of business logic realization, but also provides standards for architecture capability access and integration, and can be used for seamless integration of each business submodule and architecture capability;

2. the method provides an integration scheme of capability protocol matching, capability units and service resources, and can well realize configurable integration capability of logic realization and architecture capability realization of each service submodule. The characteristic can endow the application with the capability of distribution or monomer, and the method can be used for strategic packaging of the application and can also be used for use scenes related to integration and assembly of fragmented service sub-modules and the like. Therefore, the technical scheme of the invention can effectively solve the problem of smooth upgrade of the existing architecture capability and the problem of multi-versioning of the service application caused by the change of the architecture capability, and simplify the production management and control logic of the service application under the scenes.

Drawings

The invention will be further described with reference to the following examples with reference to the accompanying drawings.

FIG. 1 is a flow chart of the implementation of the method for adapting to system singleization and distribution according to the present invention.

Fig. 2 is an implementation schematic diagram of an implementation apparatus adaptable to system singleization and distribution according to the present invention.

FIG. 3 is a diagram illustrating application package encapsulation implemented in the present invention.

Detailed Description

Referring to fig. 1 to 3, a method for implementing system-adaptive singulation and distribution includes the following steps:

step S1, disassembling the service application into each service sub-module according to the distributed standard, wherein each service sub-module has metadata configuration globally, and the metadata configuration of each service sub-module is used for realizing the corresponding service logic;

in the technical solution of the present invention, the modularization granularity of each service sub-module is not restricted, and in the specific implementation, the module design can be performed by using, but not limited to, a front-end and back-end separation method, micro-application, micro-service, and the like.

The metadata configuration includes metadata definitions of specific business function implementations, metadata definitions of capability protocols, or sdk interactions, and may also include other metadata configurations. That is, in the implementation, the configuration may be, but is not limited to, resource configuration, capability protocol configuration, module service configuration, and the like.

In the technical scheme of the invention, each business submodule mainly focuses on business logic realization, and for realization of specific architecture functions (such as service management, service communication, storage operation, message communication, identity authority authentication and the like), the specific architecture functions are completed through peripheral matched capability units only after interaction with corresponding capability protocols is completed. Meanwhile, in order to simplify the invocation of the capability protocol of each service submodule, the following may also be provided, but not limited to: sdk of capabilities, context annotation configuration, etc. to provide more friendly capability protocol interaction.

Step S2, each business sub-module interacts with the ability protocol, matches the corresponding ability unit through the interaction with the ability protocol, and completes the specific architecture function through the matched ability unit;

in the technical solution of the present invention, the capability protocol is an abstract representation of architecture capability, and the capability protocol describes information elements including metadata configuration, communication method, request content element, response specification, and exception branch of a specific architecture capability, and may also include other information elements. In particular implementations, this may be accomplished, but is not limited to, using, for example, JSR family specifications sdk, protocol standards sdk for some type of middleware capability, service capabilities described using a particular IDL, and the like.

Through the capability protocol of the invention, loose coupling between each service submodule and the architectural function can be well realized, so that the realization of each service submodule has better independence, and a foundation is laid for strategy subpackaging, packaging and integration in the follow-up process.

The capability unit is a specific implementation of a certain capability protocol, and corresponding to the system architecture, the capability unit can be an embedded function implementation of a certain middleware capability such as message capability, service capability, log capability and the like or a client communication agent encapsulation serving as an external independent deployment capability. The capacity units need to meet the requirement of integratable specifications, play a role of 'provider' on a supply and demand model of capacity, have high-cohesion low-coupling characteristics, can indirectly depend on other low-level capacity units, and perform contract-type protocol dynamic matching operation with a business submodule (namely 'capacity consumer'), so that even under the condition that a certain capacity protocol has multiple capacity units for realization, corresponding capacity can be found according to the capacity requirement and the integration realization. Meanwhile, each capacity unit has a complete life cycle, and capacity integration specifications need to be met during integration, so that the decoupling of capacity integration implementation is achieved.

Step S3, performing contract-type dynamic matching on the execution capacity of each service sub-module related to the target release package according to the capacity integration specification to obtain each capacity unit meeting the requirement, and integrating each capacity unit through the capacity integration container;

the step S3 specifically includes:

defining the integration mode and specification of each capacity unit to form a capacity integration specification, and providing complete integration realization for the capacity integration specification through the realization of a capacity integration container; in specific implementation, the capability integration specification defines functions including capability protocol matching, capability protocol lifecycle management, process lifecycle management, flow control, resource loading, and the like. The dependence of the capacity unit and the capacity integration container can be further decoupled by constructing a capacity integration specification, so that the diversity of the infrastructure capacity implementation is achieved;

for each service submodule related to the target publishing packet, searching metadata configuration of each service submodule in a deep traversal execution mode, dynamically matching each capacity unit meeting requirements according to capacity integration specifications and capacity protocol configuration of each service submodule, and integrating each matched capacity unit by using a capacity integration container;

the capacity integration container implementation provides a set of complete integration implementation for the capacity integration specification, can run independently and can load capacity units in a plug-in mode, and the capacity integration container implementation can be but is not limited to extensions such as: the implementation of springclosed version container, kubernets version container, etc. therefore, as long as the completeness of the implementation of the integration specification is ensured, the operable program finished products can be fused and packaged for each service submodule according to the strategy, thereby realizing the flexible packaging deployment which can adapt to the distributed and single modules.

The step S3 further includes:

the capacity integration container realizes forwarding of requested traffic to the corresponding capacity unit according to the capacity integration specification, so that forward or reverse processing of the request from the capacity integration container to the capacity unit and then to the business sub-module is realized, which is also the key point of architectural capacity infrastructure.

Step S4, parsing the content of each service sub-module related in the target publishing packet, searching and obtaining the publishing packets of the corresponding service sub-modules, and combining and packaging the obtained publishing packets into an application packet, where the application packet may be a single application packet or a micro-application packet. In specific implementation, each business sub-module can be searched or compiled in time by integrating the CI and issuing the warehouse suite, and a module packaging effect in any combination manner can be achieved by integrating and organizing resources.

Referring to fig. 1 to fig. 3, an implementation apparatus adaptable to system singleization and distribution includes a service application disassembling module, a capability matching module, a capability integrating module, and an application package packaging module;

the business application disassembling module is used for disassembling business application into each business sub-module according to a distributed standard, each business sub-module has metadata configuration globally, and corresponding business logic is realized by configuring the metadata of each business sub-module;

in the technical solution of the present invention, the modularization granularity of each service sub-module is not restricted, and in the specific implementation, the module design can be performed by using, but not limited to, a front-end and back-end separation method, micro-application, micro-service, and the like.

The metadata configuration includes metadata definitions of specific business function implementations, metadata definitions of capability protocols, or sdk interactions, and may also include other metadata configurations. That is, in the implementation, the configuration may be, but is not limited to, resource configuration, capability protocol configuration, module service configuration, and the like.

In the technical scheme of the invention, each business submodule mainly focuses on business logic realization, and for realization of specific architecture functions (such as service management, service communication, storage operation, message communication, identity authority authentication and the like), the specific architecture functions are completed through peripheral matched capability units only after interaction with corresponding capability protocols is completed. Meanwhile, in order to simplify the invocation of the capability protocol of each service submodule, the following may also be provided, but not limited to: sdk of capabilities, context annotation configuration, etc. to provide more friendly capability protocol interaction.

The capability matching module is used for interacting each service sub-module with a capability protocol, matching the service sub-modules with corresponding capability units through interaction with the capability protocol, and completing specific architecture functions through the matched capability units;

in the technical solution of the present invention, the capability protocol is an abstract representation of architecture capability, and the capability protocol describes information elements including metadata configuration, communication method, request content element, response specification, and exception branch of a specific architecture capability, and may also include other information elements. In particular implementations, this may be accomplished, but is not limited to, using, for example, JSR family specifications sdk, protocol standards sdk for some type of middleware capability, service capabilities described using a particular IDL, and the like.

Through the capability protocol of the invention, loose coupling between each service submodule and the architectural function can be well realized, so that the realization of each service submodule has better independence, and a foundation is laid for strategy subpackaging, packaging and integration in the follow-up process.

The capability unit is a specific implementation of a certain capability protocol, and corresponding to the system architecture, the capability unit can be an embedded function implementation of a certain middleware capability such as message capability, service capability, log capability and the like or a client communication agent encapsulation serving as an external independent deployment capability. The capacity units need to meet the requirement of integratable specifications, play a role of 'provider' on a supply and demand model of capacity, have high-cohesion low-coupling characteristics, can indirectly depend on other low-level capacity units, and perform contract-type protocol dynamic matching operation with a business submodule (namely 'capacity consumer'), so that even under the condition that a certain capacity protocol has multiple capacity units for realization, corresponding capacity can be found according to the capacity requirement and the integration realization. Meanwhile, each capacity unit has a complete life cycle, and capacity integration specifications need to be met during integration, so that the decoupling of capacity integration implementation is achieved.

The capability integration module is used for carrying out contract type dynamic matching on the execution capability of each service sub-module related to the target release package according to the capability integration specification to obtain each capability unit meeting the requirement, and integrating each capability unit through the capability integration container;

the capability integration module is specifically as follows:

defining the integration mode and specification of each capacity unit to form a capacity integration specification, and providing complete integration realization for the capacity integration specification through the realization of a capacity integration container; in specific implementation, the capability integration specification defines functions including capability protocol matching, capability protocol lifecycle management, process lifecycle management, flow control, resource loading, and the like. The dependence of the capacity unit and the capacity integration container can be further decoupled by constructing a capacity integration specification, so that the diversity of the infrastructure capacity implementation is achieved;

for each service submodule related to the target publishing packet, searching metadata configuration of each service submodule in a deep traversal execution mode, dynamically matching each capacity unit meeting requirements according to capacity integration specifications and capacity protocol configuration of each service submodule, and integrating each matched capacity unit by using a capacity integration container;

the capacity integration container implementation provides a set of complete integration implementation for the capacity integration specification, can run independently and can load capacity units in a plug-in mode, and the capacity integration container implementation can be but is not limited to extensions such as: the implementation of springclosed version container, kubernets version container, etc. therefore, as long as the completeness of the implementation of the integration specification is ensured, the operable program finished products can be fused and packaged for each service submodule according to the strategy, thereby realizing the flexible packaging deployment which can adapt to the distributed and single modules.

The capability integration module further comprises:

the capacity integration container realizes forwarding of requested traffic to the corresponding capacity unit according to the capacity integration specification, so that forward or reverse processing of the request from the capacity integration container to the capacity unit and then to the business sub-module is realized, which is also the key point of architectural capacity infrastructure.

The application package packaging module is used for analyzing the content of each service submodule related in the target publishing package, searching and acquiring the publishing package of the corresponding service submodule, and combining and packaging the acquired publishing packages into the application package, wherein the application package can be a single application package or a micro-application package. In specific implementation, each business sub-module can be searched or compiled in time by integrating the CI and issuing the warehouse suite, and a module packaging effect in any combination manner can be achieved by integrating and organizing resources.

In summary, the invention has the following advantages:

1. the method can perform abstract decoupling on business logic realization and architecture capability realization, not only can maintain independence of business logic realization, but also provides standards for architecture capability access and integration, and can be used for seamless integration of each business submodule and architecture capability;

2. the method provides an integration scheme of capability protocol matching, capability units and service resources, and can well realize configurable integration capability of logic realization and architecture capability realization of each service submodule. The characteristic can endow the application with the capability of distribution or monomer, and the method can be used for strategic packaging of the application and can also be used for use scenes related to integration and assembly of fragmented service sub-modules and the like. Therefore, the technical scheme of the invention can effectively solve the problem of smooth upgrade of the existing architecture capability and the problem of multi-versioning of the service application caused by the change of the architecture capability, and simplify the production management and control logic of the service application under the scenes.

Although specific embodiments of the invention have been described above, it will be understood by those skilled in the art that the specific embodiments described are illustrative only and are not limiting upon the scope of the invention, and that equivalent modifications and variations can be made by those skilled in the art without departing from the spirit of the invention, which is to be limited only by the appended claims.

Claims (6)

1. A method for realizing the adaptation to the system singleization and the distribution is characterized in that: the method comprises the following steps:

step S1, disassembling the service application into each service sub-module according to the distributed standard, wherein each service sub-module has metadata configuration globally, and the metadata configuration of each service sub-module is used for realizing the corresponding service logic; the metadata configuration comprises metadata definitions of specific business function implementations, metadata definitions of capability protocols, or sdk interactions;

step S2, each business sub-module interacts with the ability protocol, matches the corresponding ability unit through the interaction with the ability protocol, and completes the specific architecture function through the matched ability unit;

step S3, defining the integration mode and specification of each ability unit to form an ability integration specification, and providing complete integration realization for the ability integration specification through the realization of an ability integration container;

for each service submodule related to the target publishing packet, searching metadata configuration of each service submodule in a deep traversal execution mode, dynamically matching each capacity unit meeting requirements according to capacity integration specifications and capacity protocol configuration of each service submodule, and integrating each matched capacity unit by using a capacity integration container;

step S4, analyzing the content of each service sub-module related in the target publishing packet, searching and obtaining the publishing packets of the corresponding service sub-modules, and combining and packaging the obtained publishing packets into an application packet.

2. The method for realizing adaptable system singleization and distribution according to claim 1, wherein: the capability protocol is an abstract representation of architectural capabilities, describing information elements including metadata configuration, communication, request content elements, response specifications, and exception branches for a particular architectural capability.

3. The method for realizing adaptable system singleization and distribution according to claim 1, wherein: the step S3 further includes:

the capacity integration container realizes the forwarding of the requested flow to the corresponding capacity unit according to the capacity integration specification, thereby realizing the forward or reverse processing of the request from the capacity integration container to the capacity unit and then to the business submodule.

4. An apparatus for realizing system singleization and distribution, comprising: the realization device comprises a business application disassembling module, a capability matching module, a capability integration module and an application package packaging module;

the business application disassembling module is used for disassembling business application into each business sub-module according to a distributed standard, each business sub-module has metadata configuration globally, and corresponding business logic is realized by configuring the metadata of each business sub-module; the metadata configuration comprises metadata definitions of specific business function implementations, metadata definitions of capability protocols, or sdk interactions;

the capability matching module is used for interacting each service sub-module with a capability protocol, matching the service sub-modules with corresponding capability units through interaction with the capability protocol, and completing specific architecture functions through the matched capability units;

the capacity integration module is used for defining the integration mode and the specification of each capacity unit to form a capacity integration specification and providing complete integration realization for the capacity integration specification through the realization of a capacity integration container;

for each service submodule related to the target publishing packet, searching metadata configuration of each service submodule in a deep traversal execution mode, dynamically matching each capacity unit meeting requirements according to capacity integration specifications and capacity protocol configuration of each service submodule, and integrating each matched capacity unit by using a capacity integration container;

and the application package packaging module is used for analyzing the content of each service submodule related in the target issuing package, searching and acquiring the issuing package of the corresponding service submodule, and combining and packaging the acquired issuing packages into the application package.

5. The apparatus of claim 4, wherein the apparatus is further configured to: the capability protocol is an abstract representation of architectural capabilities, describing information elements including metadata configuration, communication, request content elements, response specifications, and exception branches for a particular architectural capability.

6. The apparatus of claim 4, wherein the apparatus is further configured to: the capability integration module further comprises:

the capacity integration container realizes the forwarding of the requested flow to the corresponding capacity unit according to the capacity integration specification, thereby realizing the forward or reverse processing of the request from the capacity integration container to the capacity unit and then to the business submodule.

Images