CN115437807A

CN115437807A - Method and device for calling SAAS (software as a service) extended application and electronic equipment

Info

Publication number: CN115437807A
Application number: CN202211078021.6A
Authority: CN
Inventors: 赵宏波
Original assignee: Duodian Life Chengdu Technology Co ltd
Current assignee: Duodian Life Chengdu Technology Co ltd
Priority date: 2022-09-05
Filing date: 2022-09-05
Publication date: 2022-12-06

Abstract

The invention provides a method and a device for calling an SAAS extended application and electronic equipment, relates to the technical field of software-as-a-service, and solves the technical problem of low service efficiency of providing personalized service for a user by an existing SAAS multi-tenant system. The method comprises the following steps: acquiring an application request of a client, and determining a target SAAS extended application corresponding to the application request; determining a remote service type corresponding to a target SAAS extended application; constructing an extended service reference based on the remote service type; remotely calling the target SAAS extension application by the extension service reference; and providing the application service of the target SAAS extended application for the client.

Description

Method and device for calling SAAS (software as a service) extended application and electronic equipment

Technical Field

The present application relates to the field of software as a service technology, and in particular, to a method and an apparatus for invoking an SAAS extension application, and an electronic device.

Background

In a Software-as-a-Service (SAAS) -based multi-tenant system, a platform bears core services of hundreds of tenants, and due to Service characteristics of enterprise clients, each tenant is determined to have more or less personalized customization requirements, and with the rapid increase of the number of tenants, the customization requirements are increased, the contents to be maintained are increased, and the Service efficiency is low.

Therefore, for the prior art, there is a technical problem that the service efficiency of the existing SAAS multi-tenant system for providing personalized services to users is low.

Disclosure of Invention

The application aims to provide a method and a device for calling an SAAS extension application and electronic equipment, so as to solve the technical problem that the service efficiency of the existing SAAS multi-tenant system for providing personalized service for a user is low.

In a first aspect, an embodiment of the present application provides a method for calling an SAAS extension application, where the method includes:

acquiring an application request of a client, and determining a target SAAS extended application corresponding to the application request;

determining a remote service type corresponding to the target SAAS extended application;

constructing an extended service reference based on the remote service type;

remotely calling the target SAAS extended application through the extended service reference;

and providing the application service of the target SAAS extended application for the client.

In a possible implementation, the obtaining an application request of a client and determining a target SAAS extended application corresponding to the application request include:

acquiring an application request of a client through an extension point loading interception module;

and determining a target SAAS extension application corresponding to the application request through a tenant configuration platform and an extension service registration center based on the application request.

In a possible implementation, after obtaining the application request of the client and determining the target SAAS extension application corresponding to the application request, the method further includes:

judging whether the target SAAS expansion application exists in a remote server side through an expansion point proxy module;

if the judgment result is negative, locally calling the target SAAS extended application;

and if so, determining the remote service type corresponding to the target SAAS extended application.

In one possible implementation, the determining a remote service type corresponding to the target SAAS extended application includes:

and determining the remote service type corresponding to the target SAAS extension application through an extension point routing module.

In one possible implementation, the building an extended service reference based on the remote service type includes:

and constructing an extended service reference based on the remote service type, and storing the extended service reference in a remote service caching module.

In one possible implementation, the method further comprises:

detecting whether the extended service reference is stored in the remote service cache module;

and if the detection result is yes, acquiring the extended service reference from the remote service cache, and remotely calling the target SAAS extended application through the extended service reference.

In one possible implementation, the remote service type includes any one or more of:

DUBBO service, FEIGN service.

In a second aspect, an embodiment of the present application provides an apparatus for invoking an SAAS extended application, where the apparatus includes:

the system comprises an acquisition module, a processing module and a display module, wherein the acquisition module is used for acquiring an application request of a client and determining a target SAAS extended application corresponding to the application request;

a determining module, configured to determine a remote service type corresponding to the target SAAS extension application;

the construction module is used for constructing an extended service reference based on the remote service type;

the calling module is used for remotely calling the target SAAS extension application through the extension service reference;

and the providing module is used for providing the application service of the target SAAS extension application for the client.

In a third aspect, an embodiment of the present application provides an electronic device, which includes a memory and a processor, where the memory stores a computer program that is executable on the processor, and the processor implements the steps of the method according to the first aspect when executing the computer program.

In a fourth aspect, embodiments of the present application provide a computer-readable storage medium storing computer-executable instructions that, when invoked and executed by a processor, cause the processor to perform the steps of the method of the first aspect.

The embodiment of the application brings the following beneficial effects:

the embodiment of the application provides a method and a device for calling an SAAS extended application and electronic equipment. In the scheme, the extension service quotation is constructed according to the user requirements, and the extension application service required by the user is remotely called from the external SAAS application market, so that the independent development and programming according to the user requirements are avoided, the high-efficiency support on the customized requirements of the user is realized, the development and test period is obviously shortened, the system stability is improved, the research and development cost is reduced, and the technical problem of low service efficiency of providing the personalized service for the user by the conventional SAAS multi-tenant system is solved.

Drawings

In order to more clearly illustrate the detailed description of the present application or the technical solutions in the prior art, the drawings needed to be used in the detailed description of the present application or the prior art description will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative efforts.

Fig. 1 is a schematic flowchart of a method for calling an SAAS extended application according to an embodiment of the present application;

fig. 2 is a schematic structural diagram of a calling system of an SAAS extended application according to an embodiment of the present application;

fig. 3 is a schematic flowchart of a specific implementation of a method for invoking an SAAS extended application according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of a calling device for an SAAS extended application according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

To make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions of the present application will be clearly and completely described below with reference to the accompanying drawings, and it is obvious that the described embodiments are some, but not all embodiments of the present application. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application without making any creative effort belong to the protection scope of the present application.

The terms "comprising" and "having," and any variations thereof, as referred to in the embodiments of the present application, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements but may alternatively include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

In a multi-tenant system based on SAAS, a platform carries core services of hundreds of tenants, and it is determined that each tenant has more or less personalized customization requirements, and with a rapid increase in the number of tenants, the customization requirements will increase more and more, and in general, when the number of tenants is less than 10, the implementation may be implemented in a hard coding manner, for example: the method of adding conditional branches to the code to implement function routing of different tenants has a fatal problem that, as the number of tenants increases, the maintainability of the code becomes worse and worse, and finally the maintainability becomes impossible. Moreover, once each different tenant increases the customized function requirement, for the stability of the system, a tester has to perform regression verification test on all relevant functions of all tenants before online, and as the number of tenants increases, the time required for regression increases.

In the prior art, two solutions are mainly provided, the first solution is realized through a tenant routing mode, but the implementation needs to couple tenants into specific codes, when future tenants are more and a same logic multiple tenants are shared, classes marked with cxrouters need to be added with tenant identifications, so that missing is easy to occur, the expansibility is not flexible enough, tenant-oriented programming is still needed in the development process, the later development cost is higher and higher, the delivery efficiency is greatly reduced, and the cost for starting up new people is also high. The second is to implement routing of multi-tenant functions by adding conditional branches to function modules, but as the number of tenants increases, maintenance of module codes becomes more difficult, and the period of development and test regression become longer until the modules are not maintainable.

Based on this, the embodiment of the application provides a method, a device and an electronic device for invoking an SAAS extended application, and the method provided by the embodiment of the application can alleviate the technical problem that the service efficiency of the existing SAAS multi-tenant system for providing personalized services for users is low.

The embodiments of the present application will be further described with reference to the accompanying drawings.

Fig. 1 is a schematic flowchart of a method for calling an SAAS extended application according to an embodiment of the present application. As shown in fig. 1, the method includes:

step S110, obtaining an application request of the client, and determining a target SAAS extended application corresponding to the application request.

Illustratively, as shown in fig. 2, the system includes a SAAS service platform, an extension point package, a SAAS application duration, a tenant configuration platform, and an extension point service registry. The SAAS service platform is an environment for running SAAS application, a plurality of application instances are deployed in the environment, and the SAAS application realizes an interface provided in an extension point package and serves as default function realization in a standard product; the extension point packet is a JAR packet file formed by JAVA interfaces which can be developed by each system in an extension way and dependent JAVA Beans; the SAAS application market is used for realizing a deployment environment of an application of an interface in an extension point; the tenant configuration platform is used for configuring which application provides extension service for the tenant based on a certain extension point; and the extension point service registration center is used for storing the extension service provided by the extension application for the SAAS application to call. The SAAS application realizes an interface provided in an extension point package as a default function in a standard product, then the extension service application realizes the interface provided in the extension point package and releases the interface to an application market, after the extension application is deployed, a system automatically registers a service provider to an extension service registration center, and a specific application provider of an extension point is configured through a tenant configuration platform.

In practical application, an SAAS service platform in the system first receives an application request from a client, and if the SAAS service platform includes the application service, the application request is directly called locally. And if the application service is not included in the SAAS service platform, determining the application as the target SAAS extension application.

Step S120, determining a remote service type corresponding to the target SAAS extension application.

For example, after determining the target SAAS extension application corresponding to the application request, the system may further determine a remote service type corresponding to the target SAAS extension application, for example, a DUBBO service or a FEIGN service.

And step S130, constructing an extended service reference based on the remote service type.

For example, the system may build extended service references according to different service types. For example, if the remote service provider service publication type is DUBBO, a DUBBO service reference is constructed by a DUBBO service construction module; if the remote service provider service release type is FEIGN, a FEIGN service reference is constructed by a FEIGN service construction module.

Step S140, the target SAAS extension application is remotely called through the extension service reference.

Illustratively, the SAAS application reads detailed information of an extension point service provider from an extension point registration center through tenant configuration information, and invokes extension point services provided by extension applications in an SAAS application market in the running process to complete remote invocation of a target SAAS extension application.

Step S150, providing the application service of the target SAAS extension application for the client.

For example, after the system completes remote invocation of the target SAAS extension application, the corresponding application service can be provided for the client.

In the embodiment of the application, an application request of a client is obtained firstly, a target SAAS extended application corresponding to the application request is determined, a remote service type corresponding to the target SAAS extended application is determined, an extended service citation is constructed based on the remote service type, so that the target SAAS extended application is remotely called through the extended service citation, the application service of the target SAAS extended application is provided for the client, the extended service citation is constructed according to the user requirement, the extended application service required by a user is remotely called from an external SAAS application market, development and programming are avoided being independently carried out according to the user requirement, efficient support for the user customization requirement is achieved, the development and testing period is obviously shortened, the system stability is improved, the research and development cost is reduced, and the technical problem that the service efficiency of an existing SAAS multi-tenant system for providing personalized service for the user is low is solved.

The above steps are described in detail below.

In some embodiments, the step S110 may specifically include the following steps:

step a), acquiring an application request of a client through an extension point loading and intercepting module.

And b), based on the application request, determining a target SAAS extension application corresponding to the application request through a tenant configuration platform and an extension service registration center.

Illustratively, as shown in fig. 3, a user initiates an application request from a browser end (client), the application request passes through an extension point loading interception module inside the system, in the extension point loading interception module, metadata is implemented by pulling a configured remote extension point of a tenant from a tenant configuration platform, and a target SAAS extension application corresponding to the application request is determined through the tenant configuration platform and an extension service registry.

The system obtains the application request of the client by using the extension point loading interception module, and determines the target SAAS extended application corresponding to the application request through the tenant configuration platform and the extended service registration center based on the application request, so that the personalized service type requested by the user can be determined more accurately, further, the next step of processing can be performed according to the type, and the service efficiency of providing personalized service for the user is improved.

In some embodiments, after the step S110, the method may further include the steps of:

and c), judging whether the target SAAS extension application exists in the remote server side through the extension point agent module.

And d), if the judgment result is negative, locally calling the target SAAS extended application.

And e), if the judgment result is yes, determining the remote service type corresponding to the target SAAS extended application.

For example, as shown in fig. 3, after the system determines that the application request corresponds to a target SAAS extension application, the system may determine, through an extension point proxy module, whether a corresponding remote service implementation exists at a current extension point, and if the remote service implementation does not exist, execute a default implementation class in a local container Java virtual machine. If the remote implementation exists, the type of the service remote service provider is judged, and then the remote service is convenient to call.

The system judges whether the target SAAS extended application exists in the remote service end through the extended point agent module, if not, the target SAAS extended application is called locally, and if so, the remote service type corresponding to the target SAAS extended application is determined, so that the user can obtain the corresponding personalized service, and the service efficiency of providing the personalized service for the user can be improved.

In some embodiments, the step S120 may specifically include the following steps:

and f), determining the remote service type corresponding to the target SAAS extension application through the extension point routing module.

Illustratively, as shown in FIG. 3, the system may determine the type of service remote service provider by the extension point routing module. For example, the extension point routing module may determine that the remote service provider service issuance type is DUBBO or FEIGN, and may construct a corresponding service reference in a targeted manner.

The system determines the remote service type corresponding to the target SAAS extension application by using the extension point routing module, so that the remote service type can be accurately judged, remote service calling can be accurately realized, and service efficiency is improved.

In some embodiments, the step S130 may specifically include the following steps:

and g), constructing an extended service reference based on the remote service type, and storing the extended service reference in a remote service cache module.

Illustratively, as shown in FIG. 3, the system may build an extended service reference based on the remote service type. For example, if the remote service provider service release type is DUBBO, a DUBBO service reference is constructed through a DUBBO service construction module, and the service calling is completed; and if the service release type of the remote service provider is FEIGN, constructing a FEIGN service reference through a FEIGN service construction module, and completing the calling of the service. After the corresponding extended service quotation is constructed, the system can store the extended service quotation in the remote service cache module, so that the extended service quotation can be directly called from the remote service cache module at the later stage without reconstruction, and the service efficiency is improved.

Based on the step g), the method may further include the steps of:

and h), detecting whether the remote service cache module stores the extended service reference.

And i), if the detection result is yes, acquiring the extended service reference from the remote service cache, and remotely calling the target SAAS extended application through the extended service reference.

Illustratively, as shown in FIG. 3, the extended routing module in the system preferentially reads remote service objects, i.e., extended service references, from the remote service caching module. And if the remote service caching module stores the extended service reference, directly calling. And if the remote service caching module does not store the extended service reference, constructing the extended service reference based on the remote service type. The construction of the service reference object is performed, for example, by a DUBBO service construction module or a FEIGN service construction module.

The system firstly detects whether the extended service quotation is stored in the remote service cache module, if so, the extended service quotation is obtained from the remote service cache, and the target SAAS extended application is remotely called through the extended service quotation, so that the waste of resources can be avoided, the response time can be reduced, and the service efficiency of providing personalized service for users can be effectively improved.

In some embodiments, the remote service type includes any one or more of:

DUBBO service, FEIGN service.

The remote service types comprise a plurality of types, so that the functions can be richer, more types of service types can be remotely called, more comprehensive service is provided for the user, and the service efficiency of providing personalized service for the user is effectively improved.

Fig. 4 is a schematic structural diagram of a calling device for an SAAS extended application according to an embodiment of the present application. As shown in fig. 4, the call 400 of the SAAS extension application includes:

an obtaining module 401, configured to obtain an application request of a client, and determine a target SAAS extended application corresponding to the application request;

a determining module 402, configured to determine a remote service type corresponding to a target SAAS extension application;

a construction module 403, configured to construct an extended service reference based on the remote service type;

a calling module 404, configured to remotely call the target SAAS extension application through the extension service reference;

a providing module 405 is configured to provide an application service of the target SAAS extended application for the client.

In some embodiments, the obtaining module 401 is specifically configured to:

and based on the application request, determining a target SAAS extended application corresponding to the application request through a tenant configuration platform and an extended service registration center.

In some embodiments, the apparatus may further comprise:

the system comprises a judging module, an expansion point agent module and a remote server, wherein the judging module is used for acquiring an application request of a client, determining whether a target SAAS expansion application corresponding to the application request exists in the remote server or not through the expansion point agent module after determining the target SAAS expansion application;

if the judgment result is negative, the local calling is carried out on the target SAAS expansion application;

In some embodiments, the determining module 402 is specifically configured to:

In some embodiments, the building module 403 is specifically configured to:

In some embodiments, the apparatus may further comprise:

the checking module is used for detecting whether the remote service caching module stores the extended service reference;

In some embodiments, the remote service type includes any one or more of:

DUBBO service, FEIGN service.

The device provided by the embodiment of the present invention has the same implementation principle and technical effect as the method embodiments, and for the sake of brief description, no mention is made in the system embodiments, and reference may be made to the corresponding contents in the method embodiments.

The embodiment of the invention provides electronic equipment, which particularly comprises a processor and a storage device; the storage means has stored thereon a computer program which, when executed by the processor, performs the method of any of the above embodiments.

Fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present invention, where the electronic device includes: the system comprises a processor 501, a memory 502, a bus 503 and a communication interface 504, wherein the processor 501, the communication interface 504 and the memory 502 are connected through the bus 503; the processor 501 is arranged to execute executable modules, such as computer programs, stored in the memory 502.

The Memory 502 may include a high-speed Random Access Memory (RAM) and may also include a Non-volatile Memory (Non-volatile Memory), such as at least one disk Memory. The communication connection between the network element of the system and at least one other network element is implemented through at least one communication interface 504 (which may be wired or wireless), and the internet, a wide area network, a local network, a metropolitan area network, and the like may be used.

Bus 503 may be an ISA bus, PCI bus, EISA bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one double-headed arrow is shown in FIG. 5, but this does not indicate only one bus or one type of bus.

The memory 502 is used for storing a program, the processor 501 executes the program after receiving an execution instruction, and the method performed by the apparatus defined by the flow program disclosed in any of the foregoing embodiments of the present invention may be applied to the processor 501, or implemented by the processor 501.

The processor 501 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 501. The Processor 501 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the device can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components. The various methods, steps and logic blocks disclosed in the embodiments of the present invention may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 502, and the processor 501 reads the information in the memory 502 and completes the steps of the method in combination with the hardware.

The computer program product of the readable storage medium provided in the embodiment of the present invention includes a computer readable storage medium storing a program code, and instructions included in the program code may be used to execute the method in the foregoing method embodiment, and specific implementation may refer to the foregoing method embodiment, which is not described herein again.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention or a part thereof which substantially contributes to the prior art may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk, and various media capable of storing program codes.

Finally, it should be noted that: although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art will understand that: those skilled in the art can still make modifications or changes to the embodiments described in the foregoing embodiments, or make equivalent substitutions for some features, within the scope of the disclosure; such modifications, changes or substitutions do not depart from the spirit and scope of the embodiments of the present invention, and they should be construed as being included therein. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A method for calling an SAAS extended application, the method comprising:

constructing an extended service reference based on the remote service type;

remotely calling the target SAAS extension application through the extension service reference;

2. The method of claim 1, wherein the obtaining an application request of a client and determining a target SAAS extended application corresponding to the application request comprises:

3. The method of claim 1, wherein after obtaining the application request of the client and determining the target SAAS extension application corresponding to the application request, the method further comprises:

if the judgment result is negative, the local calling is carried out on the target SAAS extended application;

4. The method of claim 1, wherein the determining the remote service type corresponding to the target SAAS extended application comprises:

5. The method of claim 1, wherein constructing an extended service reference based on the remote service type comprises:

6. The method of claim 5, further comprising:

7. The method of claim 1, wherein the remote service type comprises any one or more of:

DUBBO service, FEIGN service.

8. An apparatus for invoking SAAS extended application, the apparatus comprising:

the building module is used for building an extended service reference based on the remote service type;

the calling module is used for remotely calling the target SAAS extended application through the extended service reference;

9. An electronic device comprising a memory and a processor, wherein the memory stores a computer program operable on the processor, and wherein the processor implements the steps of the method of any of claims 1 to 7 when executing the computer program.

10. A computer readable storage medium having stored thereon computer executable instructions which, when invoked and executed by a processor, cause the processor to execute the method of any of claims 1 to 7.