A multi-tenant data processing method and device based on SaaS

Abstract

The application discloses a kind of multi-tenant data processing method and device based on SaaS, and it is related to computer technical field.The specific embodiment of the method includes: obtaining the business data of the service provider corresponding to multi-tenant, and dividing business scene according to business data;Wherein, the number of service providers is at least one;SaaS database is constructed based on business data and its corresponding business scene;In response to the data acquisition request initiated by tenant, corresponding target data is obtained from SaaS database, and target data is sent to tenant;Wherein, tenant refers to the user who rents data storage space from service provider, and multi-tenant includes at least two tenants who adopt different data storage mode.The embodiment realizes the unified management of service provider information between multi-tenant, meets the demand that tenant wants to realize part data sharing, reduces the development and scalability cost of application program, improves data utilization, and improves user experience.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, in particular to a multi-tenant data processing method and device based on SaaS. BACKGROUND

[0002] Multi-tenancy technology (or multi-rental technology, SaaS for short) is a software architecture technology, which realizes how to share the same system or program component in a multi-user environment and ensures the isolation of data between users. In the current cloud computing era, multi-tenancy technology provides the same or even customized services to most clients in a single system architecture and service in a shared data center, while still ensuring the data isolation of customers.

[0003] At least the following problems exist in the prior art:

[0004] In the existing multi-tenant data processing method, the service provider information between the multi-tenants is difficult to manage uniformly due to database isolation, and the demand for sharing part of the data between tenants cannot be met, the development and scalability cost of the application program is high, the data utilization rate is low, and the user experience is poor. SUMMARY

[0005] Therefore, the embodiments of the present application provide a multi-tenant data processing method and device based on SaaS, which can realize the unified management of the service provider information between the multi-tenants, meet the demand for sharing part of the data between tenants, reduce the development and scalability cost of the application program, improve the data utilization rate, and improve the user experience.

[0006] To achieve the above object, according to the first aspect of the embodiments of the present application, a multi-tenant data processing method based on SaaS is provided, comprising:

[0007] Obtaining the business data of the service provider corresponding to the multi-tenant, and dividing the business scene according to the business data; wherein the number of service providers is at least one;

[0008] Constructing a SaaS database based on the business data and the corresponding business scene;

[0009] In response to the data acquisition request initiated by the tenant, obtaining the corresponding target data from the SaaS database, and sending the target data to the tenant;

[0010] Wherein, the tenant refers to a user who rents a data storage space from a service provider, and the multi-tenant includes at least two tenants with different data storage methods.

[0011] Further, the step of obtaining the business data of the service provider corresponding to the multi-tenant, and dividing the business scene according to the data type of the business data further comprises:

[0012] determining service data of the service provider according to historical interaction data between the multi-tenant and the service provider corresponding thereto;

[0013] obtaining the service data, and dividing a service scenario according to a service type corresponding to the service data, wherein the service scenario comprises a registration scenario, an audit scenario, a login scenario, and an information management scenario.

[0014] Further, after the step of obtaining the service data, the method further comprises:

[0015] summarizing and de-duplicating the service data.

[0016] Further, after the step of dividing the service scenario according to the service type corresponding to the service data, the method further comprises:

[0017] obtaining service data corresponding to a service requirement of the multi-tenant, and updating the service scenario according to the service data corresponding to the service requirement.

[0018] Further, the step of constructing the SaaS database based on the service data and the service scenario corresponding thereto further comprises:

[0019] obtaining service provider information corresponding to the service data;

[0020] constructing a SaaS service platform connected to the service provider based on the service provider information, the service data, and the service scenario corresponding thereto, wherein the SaaS service platform comprises a message middleware and a SaaS database.

[0021] Further, after the step of constructing the SaaS database based on the service data and the service scenario corresponding thereto, the method further comprises:

[0022] obtaining interaction data between the multi-tenant and the service provider corresponding thereto, updating the service data according to the interaction data, and updating corresponding data in the SaaS database according to the updated service data.

[0023] Further, the step of obtaining the interaction data between the multi-tenant and the service provider corresponding thereto comprises:

[0024] monitoring a business node at which the multi-tenant and the service provider interact with each other, and respectively establishing a business message queue for each business node;

[0025] sending the interaction data generated at the business node to the business message queue, and obtaining the interaction data from the business message queue.

[0026] Further, the method further comprises:

[0027] monitoring a message log corresponding to the business message queue,

[0028] determining whether the message log is an information sending failure log;

[0029] If yes, storing the interaction data indicated by the information sending failure log to the SaaS database.

[0030] Further, storing the interaction data indicated by the information sending failure log to the SaaS database further comprises:

[0031] setting a scheduling period, and storing the interaction data indicated by the information sending failure log to the SaaS database according to the scheduling period.

[0032] Further, the data storage mode comprises:

[0033] performing data storage in the form of an independent database, performing data storage in the form of a shared database and an isolated data architecture, and performing data storage in the form of a shared database and a shared data architecture.

[0034] Further, the method further comprises:

[0035] adjusting the data storage mode corresponding to each tenant according to the tenancy status and tenancy demand of the multi-tenancy.

[0036] According to a second aspect of the embodiment of the present application, a multi-tenancy data processing apparatus based on SaaS is provided, comprising:

[0037] a business data acquisition module, configured to acquire business data of a service provider corresponding to multi-tenancy, and divide business scenarios according to the business data; wherein the number of the service providers is at least one;

[0038] a database construction module, configured to construct a SaaS database based on the business data and the corresponding business scenarios thereof;

[0039] a data processing module, configured to acquire corresponding target data from the SaaS database in response to a data acquisition request initiated by a tenant, and send the target data to the tenant;

[0040] wherein the tenant refers to a user who rents a data storage space from the service provider, and the multi-tenancy comprises at least two tenants who adopt different data storage modes.

[0041] Further, the database construction module is further configured to:

[0042] acquire service provider information corresponding to the business data;

[0043] construct a SaaS service platform connected to the service provider based on the service provider information, the business data and the corresponding business scenarios thereof, wherein the SaaS service platform comprises a message middleware and a SaaS database.

[0044] According to a third aspect of the embodiments of the present application, an electronic device is provided, comprising:

[0045] one or more processors;

[0046] a storage device configured to store one or more programs,

[0047] When the one or more programs are executed by the one or more processors, the one or more processors implement any of the above SaaS-based multi-tenant data processing methods.

[0048] According to a fourth aspect of the embodiments of the present application, a computer readable medium is provided, which stores a computer program, and the program is executed by a processor to implement any of the above SaaS-based multi-tenant data processing methods.

[0049] One embodiment of the above application has the following advantages or beneficial effects: because the business data of the service provider corresponding to the multi-tenant is obtained, the business scenarios are divided according to the business data; wherein the number of service providers is at least one; the SaaS database is constructed based on the business data and the corresponding business scenarios; in response to the data acquisition request initiated by the tenant, the corresponding target data is obtained from the SaaS database, and the target data is sent to the tenant; wherein the tenant refers to a user who rents a data storage space from a service provider, and the multi-tenant includes at least two tenants who adopt different data storage methods. Therefore, the technical problems that the service provider information between the multi-tenants is difficult to manage uniformly, the demand of the tenants to realize partial data sharing cannot be met, the development and scalability cost of the application program is high, the data utilization rate is low, and the user experience is poor in the existing multi-tenant data processing method are overcome, and the technical effects of realizing the unified management of the service provider information between the multi-tenants, meeting the demand of the tenants to realize partial data sharing, reducing the development and scalability cost of the application program, improving the data utilization rate, and improving the user experience are achieved.

[0050] The further effects of the above-mentioned non-conventional optional mode will be described in the following combined with the specific embodiments. BRIEF DESCRIPTION OF DRAWINGS

[0051] The accompanying drawings are used to better understand the present application and do not constitute an improper limitation on the present application. Among them:

[0052] Figure 1 is a schematic diagram of the main process of the SaaS-based multi-tenant data processing method provided according to the first embodiment of the present application;

[0053] Figure 2is a schematic diagram of the main flow of a SaaS-based multi-tenant data processing method according to a second embodiment of the present application;

[0054] Figure 3 is a schematic diagram of the main modules of a SaaS-based multi-tenant data processing apparatus according to an embodiment of the present application;

[0055] Figure 4 is an exemplary system architecture diagram to which embodiments of the present application can be applied;

[0056] Figure 5 is a structural schematic diagram of a computer system of a terminal device or server suitable for implementing embodiments of the present application. DETAILED DESCRIPTION

[0057] Exemplary embodiments of the present application are described below with reference to the accompanying drawings, which include various details of the embodiments of the present application to assist in understanding, and should be considered as merely exemplary. Therefore, those of ordinary skill in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present application. Also, descriptions of well-known functions and structures are omitted from the following description for the sake of clarity and brevity.

[0058] Figure 1 is a schematic diagram of the main flow of a SaaS-based multi-tenant data processing method according to a first embodiment of the present application; as Figure 1 shown, the SaaS-based multi-tenant data processing method provided by the embodiments of the present application mainly includes:

[0059] Step S101, obtaining business data of service providers corresponding to the multi-tenants, and dividing business scenarios according to the business data; wherein the number of service providers is at least one.

[0060] Since there is a need for partial data sharing between multi-tenants, by the above setting, the part of business data that can be shared is obtained from the service providers of the multi-tenants, and the business scenarios are divided according to the business data, which is conducive to subsequent integration and processing of the part of business data, and the construction of a shared database, not only meeting the needs of tenants who want to implement partial data sharing, but also realizing unified management of service provider information between multi-tenants.

[0061] Specifically, according to the embodiments of the present application, the step of obtaining business data of service providers corresponding to the multi-tenants, and dividing business scenarios according to the data types of the business data further includes:

[0062] determining the business data of the service providers according to historical interaction data between the multi-tenants and the service providers corresponding thereto;

[0063] Obtaining business data, and dividing a business scenario according to a business type corresponding to the business data, wherein the business scenario includes a registration scenario, an audit scenario, a login scenario, and an information management scenario.

[0064] Through the above setting, the business data that the multi-tenants want to share can be more accurately determined according to the historical interaction data between each tenant and the service provider corresponding thereto, and the data utilization rate of the business data is further improved; and the business scenario is divided according to the type of the business data, which helps to improve the query efficiency of the part of the business data.

[0065] Further, according to an embodiment of the present application, after the step of obtaining business data, the method further includes:

[0066] Summarizing and deduplicating the business data.

[0067] Through the above setting, the business data of the service provider corresponding to each tenant is integrated and then deduplicated, which further simplifies the subsequent process of dividing the business scenario.

[0068] Preferably, according to an embodiment of the present application, after the step of dividing the business scenario according to the business type corresponding to the business data, the method further includes:

[0069] Obtaining business data corresponding to a business requirement of the multi-tenant, and updating the business scenario according to the business data corresponding to the business requirement.

[0070] Through the above setting, the coverage range of the business data to be shared is further expanded in combination with the actual requirement of the tenant, and the user experience is further improved.

[0071] Step S102, constructing a SaaS database based on the business data and the business scenario corresponding thereto.

[0072] Specifically, according to an embodiment of the present application, the step of constructing the SaaS database based on the business data and the business scenario corresponding thereto further includes:

[0073] Obtaining service provider information corresponding to the business data;

[0074] Constructing a SaaS service platform connected to the service provider based on the service provider information, the business data, and the business scenario corresponding thereto, wherein the SaaS service platform includes a message middleware and a SaaS database.

[0075] Through the above setting, the SaaS service platform connected with the at least one service provider is constructed, the message middleware (mainly a message queue for data transmission) and the SaaS database (for storing the determined business data, i.e., the data that the tenants want to share) are constructed, the data interaction between the service provider and the tenants (tenants with different data storage modes) deployed in different environments is realized, the purpose of data sharing is achieved, the development and scalability cost of the application program is reduced, the data utilization rate is improved, and the user experience is improved.

[0076] Preferably, according to the embodiment of the present application, after the step of constructing the SaaS database based on the business data and the corresponding business scenarios, the method further comprises:

[0077] acquiring the interaction data between the multi-tenancy and the corresponding service provider, updating the business data according to the interaction data, and updating the corresponding data in the SaaS database according to the updated business data.

[0078] After the SaaS service platform is built, the interaction data between the multi-tenancy and the corresponding service provider is monitored in real time (or periodically), and the corresponding data in the database is updated to ensure that the data between the SaaS service platform and the tenants is consistent.

[0079] Further, according to the embodiment of the present application, the step of acquiring the interaction data between the multi-tenancy and the corresponding service provider comprises:

[0080] monitoring the business nodes of the multi-tenancy and the service provider for business interaction; and establishing a business message queue for each business node;

[0081] sending the interaction data generated at the business node to the business message queue, and acquiring the interaction data from the business message queue.

[0082] Through the above setting, the message synchronization mechanism is established, the data synchronization and interaction between the platform and different tenants are realized, and the data consistency between the SaaS service platform and the tenants is ensured when the corresponding tenants of the service provider register, manage information, and perform other business operations on the SaaS service platform.

[0083] Preferably, according to the embodiment of the present application, the method further comprises:

[0084] monitoring the message log corresponding to the business message queue,

[0085] determining whether the message log is an information sending failure log;

[0086] If yes, the interaction data indicated by the information sending failure log is stored in the SaaS database.

[0087] Through the above setting, the timing inspection and the completion mechanism are established, the service node is monitored through the timing inspection, the interactive data generated at the service node is acquired through the completion mechanism, and the interactive data is stored into the database, and the data consistency is further ensured.

[0088] Exemplarily, according to the embodiment of the present application, the above-mentioned storing the interactive data indicated by the information sending failure log into the SaaS database further includes:

[0089] The scheduling period is set, and the interactive data indicated by the information sending failure log is stored into the SaaS database according to the scheduling period.

[0090] According to a specific embodiment of the embodiment of the present application, the data completion service can be started by timing (for example, every half hour), the interactive data corresponding to the information sending failure log in the database is scanned, and the interactive data is sent to the corresponding tenant.

[0091] Step S103, in response to the data acquisition request initiated by the tenant, the corresponding target data is acquired from the SaaS database, and the target data is sent to the tenant.

[0092] Wherein, the tenant refers to a user who rents a data storage space from a service provider, and the multi-tenant includes at least two tenants with different data storage modes.

[0093] After the shared database (i.e. the above-mentioned SaaS database) is constructed, the corresponding target data can be directly acquired from the shared database according to the data acquisition request initiated by the tenant. Through the above setting, the unified management of the service provider information among the multi-tenants is realized, the needs of the tenants to realize the partial data sharing are met, the development and scalability cost of the application program is reduced, the data utilization rate is improved, and the technical effects of improving the user experience are improved.

[0094] Further, according to the embodiment of the present application, the above-mentioned data storage mode includes:

[0095] The data is stored in the form of independent database, the data is stored in the form of shared database and isolated data architecture, and the data is stored in the form of shared database and shared data architecture.

[0096] Wherein, the data is stored in the form of independent database refers to that one tenant corresponds to one database, the user data isolation level of this scheme is the highest, the security is the best, but the cost is higher.

[0097] The data storage in the way of sharing database and isolated data architecture means that multiple or all tenants share a database, but each tenant has a schema (also called a user). The tenants with high security requirements are provided with a certain degree of logical data isolation, which is not complete isolation; each database can support a larger number of tenants.

[0098] The data storage in the way of sharing database and sharing data architecture means that tenants share the same database and the same schema, but a TenantID multi-tenant data field is added in the table. This is the highest degree of sharing and the lowest level of isolation, but the cost is the lowest.

[0099] Preferably, according to the embodiment of the present application, the method further comprises:

[0100] According to the lease status and lease demand of the multi-tenant, the data storage mode corresponding to each tenant is adjusted.

[0101] The lease status includes tenant credit information, payment information and other information describing the current lease status of the tenant; the lease demand mainly refers to the current demand of the tenant for storage space.

[0102] Through the above setting, the data storage mode corresponding to each tenant can be adjusted according to the tenant credit information, payment information and storage space, that is, the switching between the three data storage modes is realized, and the user experience is further improved.

[0103] According to the technical scheme of the embodiment of the present application, the service data of the service provider corresponding to the multi-tenant is obtained, and the business scenarios are divided according to the business data; the number of service providers is at least one; the SaaS database is constructed based on the business data and the corresponding business scenarios; in response to the data acquisition request initiated by the tenant, the corresponding target data is obtained from the SaaS database, and the target data is sent to the tenant; the tenant refers to a user who rents a data storage space from a service provider, and the technical means of the multi-tenant includes at least two tenants with different data storage modes, so that the technical problems of the prior art, such as the difficulty in unified management of the service provider information between the multi-tenants, the inability to meet the demand of the tenants to realize partial data sharing, the high cost of application development and scalability, the low data utilization rate and the poor user experience, are overcome, and the technical effects of unified management of the service provider information between the multi-tenants, meeting the demand of the tenants to realize partial data sharing, reducing the cost of application development and scalability, improving the data utilization rate and improving the user experience are achieved.

[0104] Figure 2is a schematic diagram of a main flow of a SaaS-based multi-tenant data processing method provided according to a second embodiment of the present application; as Figure 2 As shown in the figure, the SaaS-based multi-tenant data processing method provided by the embodiment of the present application mainly includes:

[0105] In step S201, according to historical interaction data between a multi-tenant and a service provider corresponding thereto, business data of the service provider is determined, and the business data is summarized and processed for duplication removal; wherein the number of service providers is at least one.

[0106] Through the above setting, according to historical interaction data between each tenant and a service provider corresponding thereto, the business data that the multi-tenant wants to share can be more accurately determined, and thus the data utilization rate of the business data is improved.

[0107] Further, according to a specific implementation manner of the embodiment of the present application, the step of summarizing and processing the business data for duplication removal further includes:

[0108] Integrating full key data of existing suppliers of each tenant (including existing inventory supplier data under each tenant environment, and key data such as supplier enterprise basic data, supplier service area data, supplier warehousing related data, supplier contact data, supplier account information data, and supplier user data), and performing data initialization (defining data collection boundaries (when defining the boundaries, it is necessary to pay attention to removing duplicate data under each tenant to ensure the effectiveness of the collected data; at the same time, define the collection conditions, and filter the corresponding data according to the conditions)) in the SaaS database corresponding to the supplier platform (i.e. the subsequently constructed SaaS service platform connected with the service provider); collecting and integrating inventory supplier data of each tenant; synchronizing the database structure between the supplier platform and each tenant (synchronizing the database structure between the supplier platform and each tenant by using the otter tool); supplier platform data initialization (brushing the integrated full supplier data into the supplier platform database); synchronizing the data between the platform and each tenant to maintain consistency), since the supplier platform should serve as a data transfer and interaction hub, when the SaaS service platform goes online, it is necessary to ensure that the data of the SaaS service platform is the sum of the data of each tenant environment (after removing the duplicate data), and it is also necessary to integrate the inventory data under each tenant, and after removing the duplicate data, the integrated data is initialized into the database of the supplier platform (SaaS service platform) to ensure that the data corresponding to the supplier under each tenant environment is consistent when the platform goes online.

[0109] Specifically, the tenant refers to a user who rents a data storage space from a service provider, and the multi-tenant includes at least two tenants with different data storage modes.

[0110] According to the embodiment of the present application, the data storage mode includes:

[0111] The data storage is in the form of independent databases, in the form of shared databases and isolated data architectures, or in the form of shared databases and shared data architectures. The tenant data isolation level is the highest in the form of independent databases, and the security is the best, but the cost is higher. The tenant data in the form of shared databases and isolated data architectures provides a certain degree of logical data isolation, and is not completely isolated; each database can support a larger number of tenants. The data storage in the form of shared databases and shared data architectures has the highest sharing degree and the lowest isolation level, but the required cost is the lowest.

[0112] Further, according to the embodiment of the present application, the method further comprises:

[0113] According to the leasing status and leasing demand of the multi-tenant, the data storage mode corresponding to each tenant is adjusted.

[0114] The leasing status includes tenant credit information, payment information and other information describing the current leasing status of the tenant; the leasing demand mainly refers to the current demand of the tenant for storage space.

[0115] Through the above setting, the data storage mode corresponding to each tenant can be adjusted according to the tenant credit information, payment information, storage space, etc., that is, the switching between the three data storage modes of the tenant is realized, and the user experience is further improved.

[0116] Step S202, dividing the business scene according to the business data; wherein the business scene includes: registration scene, audit scene, login scene, information management scene.

[0117] Specifically, according to the embodiment of the present application, for the supplier (i.e. service provider) related data that needs to be shared between different environment tenants (i.e. tenants adopting different data storage modes), the related business scene corresponding to the supplier is abstracted. The abstracted business scene is mainly in the procurement business, high-frequency operation, and does not involve the relatively independent business interaction between the supplier and each tenant, for example, supplier registration, supplier registration audit, supplier login, supplier basic information management, supplier information change and other common business scenes of the supplier, which helps to reduce the development and scalability cost of the application program and improve the data utilization rate.

[0118] Through the above setting, the business scene is divided according to the business data, which is conducive to subsequent integration and processing of the part of the business data to build a shared database. Not only can the demand of the tenants who want to share part of the data be met, but also the unified management of the service provider information between the multi-tenants can be realized, which helps to realize the query efficiency of the part of the business data.

[0119] In step S203, the business data corresponding to the business requirement of the multi-tenancy is acquired, and the business scenario is updated according to the business data corresponding to the business requirement.

[0120] Specifically, according to the embodiment of the present application, after the stable operation of the supplier platform, some value-added business scenarios are considered, so as to facilitate the subsequent supplier to perform big data analysis, and make supplier report, etc. The business data of this part is acquired, the corresponding business scenario is expanded, and through the above setting, the coverage range of the business data to be shared is further expanded, and the user experience is further improved.

[0121] In step S204, the service provider information corresponding to the business data is acquired; and the SaaS service platform connected with the service provider is constructed based on the service provider information, the business data and the corresponding business scenario, the SaaS service platform including a message middleware and a SaaS database.

[0122] Through the above setting, the SaaS service platform connected with the at least one service provider is constructed, the message middleware (mainly a message queue, used for data transmission) and the SaaS database (used for storing the determined business data, i.e. the data to be shared between tenants, which can be a database cluster) are constructed, the data interaction between the service provider and the tenants (tenants with different data storage modes) deployed in each environment is realized, the purpose of data sharing is achieved, the development and scalability cost of the application program is reduced, the data utilization rate is improved, and the user experience is improved.

[0123] According to the embodiment of the present application, by constructing the SaaS service platform connected with the service provider, the unified analysis and management of the data entry corresponding to the multi-tenancy under the multi-mode deployment scheme is realized. By taking the supplier unified platform (SaaS service platform) as the unified entrance for the supplier registration and login, the platform stores the full amount of supplier related data, which not only meets the data interaction between the tenants and the platform, but also is beneficial to the platform to collect the business data of the same supplier under different tenants, and forms the omnibearing data analysis and management.

[0124] In step S205, in response to the data acquisition request initiated by the tenant, the corresponding target data is acquired from the SaaS database, and the target data is sent to the tenant.

[0125] The embodiment of the application mainly realizes data sharing between tenants in a multi-mode deployment scheme (multiple data storage modes), and after a shared database (i.e., the SaaS database) is constructed, target data can be directly obtained from the shared database according to a data acquisition request initiated by a tenant. Through the above setting, unified management of service provider information between multiple tenants is realized, the needs of tenants to realize partial data sharing are met, the development and scalability costs of the application program are reduced, the data utilization rate is improved, and the technical effects of improving user experience are achieved.

[0126] In step S206, the business nodes of the multi-tenant and the service provider are monitored, a business message queue is established for each business node, the interaction data generated at the business node is sent to the business message queue, the interaction data is obtained from the business message queue, the business data is updated according to the interaction data, and the corresponding data in the SaaS database is updated according to the updated business data.

[0127] Specifically, according to a specific embodiment of the embodiment of the application, the above steps actually establish a message synchronization mechanism, which includes: combing the business nodes triggering the message synchronization (such as triggering the message synchronization mechanism when the supplier registers and when the real-name authentication is performed, to ensure the consistency of the tenant and the supplier information); establishing a unified message sending window (the supplier platform is used as a unified entrance to establish a sending window, so that the supplier data is sent to each tenant from the supplier platform as a starting point); establishing a message transmission channel between the platform and the tenant in the form of a message queue; defining a responsibility chain mechanism for receiving and processing the business data sent by the message synchronization mechanism (the tenant end should define a responsibility chain, which is similar to a factory and is the driving source of the tenant end receiving data, and only a general mode needs to be defined, and subsequent processing methods corresponding to the receiving methods of each scene are output by the factory for each scene, which are used to listen to, receive and process the data transmitted by the supplier platform); instantiating corresponding responsibility chain instances according to different business scenarios to realize message receiving and processing (for example, the registration information responsibility chain needs to be instantiated, and the real-name information processing responsibility chain needs to be defined for the user real-name information).

[0128] Through the above setting, the message synchronization mechanism is established, the data synchronization and interaction between the platform and different tenants are realized, and the data consistency between the SaaS service platform and each tenant is ensured when the corresponding tenant of the service provider registers, manages information and performs other business operations on the SaaS service platform.

[0129] In step S207, the message log corresponding to the business message queue is monitored, and in the case that the message log is an information sending failure log, the interaction data indicated by the information sending failure log is stored to the SaaS database.

[0130] According to the embodiment of the present application, the above steps substantially construct the timing inspection and completion mechanism, mainly including: establishing a message queue monitoring service (for monitoring the message log (mainly the information sending failure log) of the message queue, and storing the corresponding interaction data to the database; establishing a message completion service (scanning and pulling the information sending failure log record stored in the database, and calling the corresponding interaction data for retransmission, and sending the interaction data to each tenant again); establishing a timing scheduling task (starting the message completion service through timing, for example, every half an hour, scanning the information sending failure log record in the database and retransmitting).

[0131] Through the above setting, the timing inspection and completion mechanism is established, the business nodes are monitored through the timing inspection, the interaction data generated at the business nodes are obtained through the completion mechanism, and the interaction data is stored to the database, thereby further guaranteeing the data consistency.

[0132] Exemplarily, according to the embodiment of the present application, the above storing the interaction data indicated by the information sending failure log to the SaaS database further includes:

[0133] The scheduling period is set, and the interaction data indicated by the information sending failure log is stored to the SaaS database according to the scheduling period.

[0134] According to a specific embodiment of the embodiment of the present application, the data completion service can be started through timing (for example, every half an hour), the interaction data corresponding to the information sending failure log in the database is scanned, and the interaction data is sent to the corresponding tenant.

[0135] According to the technical scheme of the embodiment of the present application, because the business data of the service provider corresponding to the multi-tenant is obtained, the business scene is divided according to the business data; wherein the number of service providers is at least one; the SaaS database is constructed based on the business data and the corresponding business scene; in response to the data acquisition request initiated by the tenant, the target data is obtained from the SaaS database, and the target data is sent to the tenant; wherein the tenant refers to a user who rents a data storage space from the service provider, and the multi-tenant includes at least two tenants which adopt different data storage methods. Therefore, the technical means overcomes the technical problems in the prior art that the service provider information of the multi-tenant is difficult to be uniformly managed, and the demand of the tenants to realize partial data sharing cannot be met, the development and scalability cost of the application program is high, the data utilization rate is low, and the user experience is poor, thereby achieving the technical effects of uniformly managing the service provider information of the multi-tenant, meeting the demand of the tenants to realize partial data sharing, reducing the development and scalability cost of the application program, improving the data utilization rate, and improving the user experience.

[0136] Figure 3is a schematic diagram of main modules of a SaaS-based multi-tenant data processing apparatus provided according to an embodiment of the present application; as Figure 3 As shown in the figure, the SaaS-based multi-tenant data processing apparatus 300 provided by the embodiment of the present application mainly comprises:

[0137] A business data acquisition module 301 is configured to acquire business data of a service provider corresponding to a multi-tenant, and divide a business scenario according to the business data; wherein the number of service providers is at least one.

[0138] Through the above setting, not only the demand of the tenants to realize partial data sharing can be met, but also the unified management of the service provider information between the multi-tenants can be realized.

[0139] Specifically, according to the embodiment of the present application, the business data acquisition module 301 is further configured to:

[0140] determine the business data of the service provider according to historical interaction data between the multi-tenant and the service provider corresponding thereto;

[0141] acquire the business data, and divide a business scenario according to a business type corresponding to the business data, wherein the business scenario comprises a registration scenario, an audit scenario, a login scenario, and an information management scenario.

[0142] Through the above setting, not only the business data that the multi-tenant wants to share can be determined more accurately, thereby improving the data utilization rate of the business data, but also the query efficiency of the part of the business data can be realized.

[0143] Further, according to the embodiment of the present application, the SaaS-based multi-tenant data processing apparatus 300 further comprises a deduplication module, which is configured to:

[0144] aggregate and deduplicate the business data.

[0145] Through the above setting, after the business data of the service provider corresponding to each tenant is integrated and deduplicated, the subsequent process of dividing the business scenario is further simplified.

[0146] Preferably, according to the embodiment of the present application, the SaaS-based multi-tenant data processing apparatus 300 further comprises an update module, which is configured to:

[0147] acquire business data corresponding to a business requirement of the multi-tenant, and update the business scenario according to the business data corresponding to the business requirement.

[0148] Through the above setting, the coverage of the business data to be shared is further expanded in combination with the actual needs of the tenants, and the user experience is further improved.

[0149] The database construction module 302 is configured to construct a SaaS database based on the business data and the corresponding business scenarios.

[0150] Specifically, according to the embodiment of the present application, the database construction module 302 is configured to:

[0151] obtain service provider information corresponding to the business data;

[0152] construct a SaaS service platform connected to the service provider based on the service provider information, the business data and the corresponding business scenarios, wherein the SaaS service platform comprises a message middleware and a SaaS database.

[0153] Through the above setting, the SaaS service platform connected to the at least one service provider is constructed, the message middleware and the SaaS database are constructed, the data interaction between the service provider and the tenants (tenants adopting different data storage modes) deployed in different environments is realized, and the purpose of data sharing is achieved.

[0154] Preferably, according to the embodiment of the present application, after the step of constructing the SaaS database based on the business data and the corresponding business scenarios, the update module is further configured to:

[0155] obtain interaction data between the multi-tenant and the corresponding service provider, update the business data according to the interaction data, and update the corresponding data in the SaaS database according to the updated business data.

[0156] By monitoring the interaction data between the multi-tenant and the corresponding service provider in real time (or periodically) and updating the corresponding data in the database, the consistency between the SaaS service platform and the tenants is ensured.

[0157] Further, according to the embodiment of the present application, the update module is further configured to:

[0158] monitor business nodes for business interaction between the multi-tenant and the service provider; and establish a business message queue for each business node;

[0159] send the interaction data generated at the business node to the business message queue, and obtain the interaction data from the business message queue.

[0160] Through the above setting, the message synchronization mechanism is established, the data synchronization and interaction between the platform and different tenants are realized, and the data consistency between the SaaS service platform and each tenant is ensured when the corresponding tenant of the service provider performs registration, information management and other business operations on the SaaS service platform.

[0161] Preferably, according to the embodiment of the present application, the SaaS-based multi-tenant data processing device 300 further comprises a monitoring module, configured to:

[0162] monitor the message log corresponding to the business message queue,

[0163] determine whether the message log is an information sending failure log;

[0164] if yes, store the interaction data indicated by the information sending failure log to the SaaS database.

[0165] Through the above setting, the timing inspection and completion mechanism is established, the business node is monitored through the timing inspection, the interaction data generated at the business node is obtained through the completion mechanism, and the interaction data is stored in the database, thereby further ensuring the data consistency.

[0166] Exemplarily, according to the embodiment of the present application, the monitoring module is further configured to:

[0167] set a scheduling period, and store the interaction data indicated by the information sending failure log to the SaaS database according to the scheduling period.

[0168] According to a specific embodiment of the present application, the data completion service can be started at a timing (for example, every half an hour), the interaction data corresponding to the information sending failure log in the database is scanned, and the interaction data is sent to the corresponding tenant.

[0169] The data processing module 303 is configured to obtain the target data from the SaaS database in response to the data acquisition request initiated by the tenant, and send the target data to the tenant.

[0170] The tenant refers to a user who rents a data storage space from the service provider, and the multi-tenant includes at least two tenants with different data storage modes.

[0171] Through the above setting, the unified management of the service provider information among the multi-tenants is realized, the needs of the tenants to share part of the data are met, the development and scalability costs of the application program are reduced, the data utilization rate is improved, and the technical effects of improving the user experience are achieved.

[0172] Further, according to the embodiment of the present application, the data storage mode comprises:

[0173] The data is stored in the form of independent database, stored in the form of shared database and isolated data architecture, or stored in the form of shared database and shared data architecture.

[0174] Among them, the tenant data isolation level of the data stored in the form of independent database is the highest, the security is the best, but the cost is higher.

[0175] The tenant data stored in the form of shared database and isolated data architecture provides a certain degree of logical data isolation, but not complete isolation; each database can support more tenants.

[0176] The data stored in the form of shared database and shared data architecture is the highest sharing and the lowest isolation, but the cost is the lowest.

[0177] Preferably, according to the embodiment of the present application, the SaaS-based multi-tenant data processing device 300 further comprises an adjusting module for:

[0178] According to the lease status and lease demand of the multi-tenant, the data storage mode corresponding to each tenant is adjusted.

[0179] Among them, the lease status includes tenant credit information, payment information and other information describing the current lease status of the tenant; the lease demand mainly refers to the current demand of the tenant for storage space.

[0180] Through the above setting, the data storage mode corresponding to each tenant can be adjusted according to the tenant credit information, payment information and storage space, that is, the switching between the three data storage modes is realized, and the user experience is further improved.

[0181] According to the technical scheme of the embodiment of the present application, the business data of the service provider corresponding to the multi-tenant is acquired, and the business data is used to divide the business scene; the number of the service provider is at least one; the SaaS database is constructed based on the business data and the corresponding business scene; the target data is acquired from the SaaS database in response to the data acquisition request initiated by the tenant, and the target data is sent to the tenant; the tenant refers to the user who rents the data storage space from the service provider, and the multi-tenant includes at least two tenants which adopt different data storage modes, so that the technical problems of the prior art, such as the difficulty in unified management of the service provider information between the multi-tenants, the inability to meet the requirement of the tenants to share part of the data, the high cost of the development and scalability of the application program, the low data utilization rate and the poor user experience, are overcome, and the technical effects of unified management of the service provider information between the multi-tenants, the meeting of the requirement of the tenants to share part of the data, the reduction of the cost of the development and scalability of the application program, the improvement of the data utilization rate and the improvement of the user experience are achieved.

[0182] Figure 4 An exemplary system architecture 400 to which the SaaS-based multi-tenant data processing method or the SaaS-based multi-tenant data processing apparatus of the embodiments of the present application can be applied is shown.

[0183] As shown in Figure 4 The system architecture 400 can include terminal devices 401, 402, 403, a network 404 and a server 405 (this architecture is only an example, and the components included in the specific architecture can be adjusted according to the specific application). The network 404 is used as a medium to provide a communication link between the terminal devices 401, 402, 403 and the server 405. The network 404 can include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0184] The user can use the terminal devices 401, 402, 403 to interact with the server 405 through the network 404 to receive or send messages, etc. Various communication client applications can be installed on the terminal devices 401, 402, 403, such as data processing applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only as an example).

[0185] The terminal devices 401, 402, 403 can be various electronic devices with a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers and desktop computers, etc.

[0186] The server 405 can be a server that provides various services, such as a server that processes data for a user using the terminal device 401, 402, 403 (as an example). The server can analyze and process received service data and the like, and feed back a processing result (e.g., target data - as an example) to the terminal device.

[0187] It should be noted that the SaaS-based multi-tenant data processing method provided by the embodiments of the present application is generally executed by the server 405, and accordingly, the SaaS-based multi-tenant data processing apparatus is generally provided in the server 405.

[0188] It should be understood that Figure 4 The number of terminal devices, networks, and servers in the system is merely illustrative. Any number of terminal devices, networks, and servers can be provided as needed.

[0189] Reference is made below to Figure 5 which shows a structural diagram of a computer system 500 suitable for implementing a terminal device or a server of the embodiments of the present application. Figure 5 The terminal device or server shown is merely an example and should not impose any limitation on the functions and use range of the embodiments of the present application.

[0190] As shown in Figure 5 , the computer system 500 includes a central processing unit (CPU) 501 that can perform various appropriate actions and processes according to programs stored in a read-only memory (ROM) 502 or programs loaded from a storage portion 508 into a random access memory (RAM) 503. Various programs and data required for the operation of the system 500 are also stored in the RAM 503. The CPU 501, the ROM 502, and the RAM 503 are connected to each other through a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

[0191] The following components are connected to the I / O interface 505: an input portion 506 including a keyboard, a mouse, and the like; an output portion 507 including a cathode ray tube (CRT), a liquid crystal display (LCD), and the like, and a speaker, and the like; a storage portion 508 including a hard disk, and the like; and a communication portion 509 including a network interface card such as a LAN card, a modem, and the like. The communication portion 509 performs communication processing via a network such as the Internet. A drive 510 is also connected to the I / O interface 505 as needed. A removable medium 511 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, and the like is mounted on the drive 510 as needed, so that a computer program read therefrom is installed in the storage portion 508 as needed.

[0192] In particular, the processes described above with reference to the flow charts can be implemented as a computer software program in accordance with the embodiments disclosed herein. For example, embodiments disclosed herein include a computer program product which includes a computer program tangibly embodied on a computer readable medium, the computer program containing program code for executing the methods illustrated by the flow charts. In such embodiments, the computer program can be downloaded and installed from a network via the communication section 509 and / or installed from the removable media 511. When the computer program is executed by the central processing unit (CPU) 501, the above-described functions defined in the system of the present application are executed.

[0193] It should be noted that the computer readable medium shown in the present application can be a computer readable signal medium or a computer readable storage medium or any combination of the two. The computer readable storage medium may, for example, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or apparatus, or any combination of the above. More specific examples of the computer readable storage medium can include, but are not limited to, an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, the computer readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, device or apparatus. In the present application, the computer readable signal medium can include a data signal carried in a baseband or as a carrier wave in a propagated data signal, in which the computer readable program code is carried. Such a propagated data signal can take many forms, including but not limited to an electromagnetic signal, an optical signal or any suitable combination of the above. The computer readable signal medium can also be any computer readable medium that can send, propagate or transfer a program for use by or in connection with an instruction execution system, device or apparatus. The program code contained on the computer readable medium can be transmitted using any suitable medium, including but not limited to wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0194] The computer program product of the present application can be a computer program embodied on a computer readable medium. The computer program product can be stored in the memory 130 and executed by the processor 120 as a computer implemented process. The computer readable medium can be a storage device such as a floppy disk, a hard disk, a CD-ROM, a DVD, a RAM, a ROM, or a flash memory, among others. The computer readable medium can be a transmittable carrier wave that is embodied on a propagated signal, with the propagated signal being transmitted by any one or more of a number of different delivery methods, including wireline, wireless, optical, electromagnetic, or any other suitable delivery method.

[0195] The modules described in the embodiments of the present application can be implemented by software, or by hardware, or by a combination of software and hardware. The modules described can be arranged in a processor, for example, a processor can be described as including a service data obtaining module, a database constructing module, and a data processing module. In some cases, the names of the modules do not constitute a limitation on the modules themselves, for example, the service data obtaining module can also be described as a module for obtaining service data of service providers corresponding to multiple tenants, and dividing business scenarios according to the service data, wherein the number of service providers is at least one.

[0196] As another aspect, the present application also provides a computer readable medium, which can be included in the device described in the above embodiments, or can exist separately without being assembled into the device. The computer readable medium carries one or more programs, which, when executed by the device, cause the device to include: obtaining service data of service providers corresponding to multiple tenants, and dividing business scenarios according to the service data, wherein the number of service providers is at least one; constructing a SaaS database based on the service data and the corresponding business scenarios; in response to a data obtaining request initiated by a tenant, obtaining corresponding target data from the SaaS database, and sending the target data to the tenant; wherein the tenant refers to a user who rents a data storage space from a service provider, and the multiple tenants include at least two tenants who adopt different data storage modes.

[0197] According to the technical scheme of the embodiment of the present application, the business data of the service provider corresponding to the multi-tenant is acquired, and the business data is used to divide the business scene; the number of the service provider is at least one; the SaaS database is constructed based on the business data and the corresponding business scene; the target data is acquired from the SaaS database in response to the data acquisition request initiated by the tenant, and the target data is sent to the tenant; the tenant refers to the user who rents the data storage space from the service provider; the multi-tenant includes at least two tenants which adopt different data storage modes; therefore, the technical scheme overcomes the technical problems in the prior art, such as the service provider information of the multi-tenant being difficult to be uniformly managed, the requirement of the tenants to share part of the data being unable to be met, the development and scalability cost of the application program being high, the data utilization rate being low, and the user experience being poor, and achieves the technical effects of uniformly managing the service provider information of the multi-tenant, meeting the requirement of the tenants to share part of the data, reducing the development and scalability cost of the application program, improving the data utilization rate, and improving the user experience.

[0198] The above detailed description does not constitute a limitation on the protection scope of the present application. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and replacements can occur depending on design requirements and other factors. Any modification, equivalent replacement, and improvement within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims

1. A SaaS-based multi-tenant data processing method, characterized by, The method comprises the following steps: According to the historical interaction data between the multi-tenant and the corresponding service provider, the service data that can be shared by the service provider is determined; A tenant refers to a user who rents data storage space from a service provider, and a multi-tenant includes at least two tenants who adopt different data storage methods; Obtain the business data, and perform aggregation and deduplication processing on the business data; Specifically, the full amount of key data of each tenant's existing supplier is integrated, and data initialization is performed on the SaaS database corresponding to the supplier platform. The otter tool is used to synchronize the database structure between the supplier platform and each tenant, and the integrated full amount of supplier data is brushed into the supplier platform database. The key data includes supplier enterprise basic data, supplier service area data, supplier warehousing related data, supplier contact data, supplier account information data, and supplier user data. The supplier platform is a SaaS service platform connected to the service provider built subsequently; According to the business type corresponding to the business data, the business scene is divided, wherein the business scene includes registration scene, audit scene, login scene, and information management scene, and the number of service providers is at least one; Based on the business data and the business scene corresponding thereto, a SaaS database is constructed; In response to a data acquisition request initiated by a tenant, corresponding target data is acquired from the SaaS database, and the target data is sent to the tenant; Wherein, the tenant refers to a user who rents data storage space from a service provider, and the multi-tenant includes at least two tenants who adopt different data storage methods; The step of constructing a SaaS database based on the business data and the business scene corresponding thereto further comprises: Obtain the service provider information corresponding to the business data; Based on the service provider information, the business data and the business scene corresponding thereto, a SaaS service platform connected to the service provider is constructed, which includes a message middleware and the SaaS database; After the step of constructing a SaaS database based on the business data and the business scene corresponding thereto, the method further comprises: Obtain the interaction data between the multi-tenant and the corresponding service provider, update the business data according to the interaction data, and update the corresponding data in the SaaS database according to the updated business data; The step of obtaining the interaction data between the multi-tenant and the corresponding service provider comprises: Monitor the business nodes of the multi-tenant and the service provider for business interaction; a business message queue is established for each business node; Send the interaction data generated at the business node to the business message queue, and obtain the interaction data from the business message queue; The method further comprises: Monitoring the message log corresponding to the business message queue, Judging whether the message log is an information sending failure log; If yes, store the interaction data indicated by the information sending failure log to the SaaS database; The method further comprises: setting a scheduling period, and storing the interaction data indicated by the information sending failure log to the SaaS database according to the scheduling period. 2.The SaaS-based multi-tenant data processing method of claim 1, wherein, The method further comprises: obtaining business data corresponding to a business requirement of the multi-tenancy, and updating the business scene according to the business data corresponding to the business requirement. 3.The SaaS-based multi-tenant data processing method of claim 1, wherein, The data storage mode comprises: independent database, shared database with isolated data architecture, and shared database with shared data architecture. 4.The SaaS-based multi-tenant data processing method of claim 3, wherein, The method further comprises: adjusting the data storage mode of each tenant according to the leasing status and leasing requirement of the multi-tenancy. 5.A SaaS-based multi-tenant data processing apparatus, characterized by comprising: The method further comprises: a business data obtaining module configured to determine shareable business data of a service provider according to historical interaction data between the multi-tenancy and the service provider corresponding thereto; a tenant refers to a user leasing a data storage space from a service provider, and the multi-tenancy comprises at least two tenants adopting different data storage modes; the business data is obtained, and the business data is aggregated and processed for deduplication; specifically, all the key data of existing suppliers of each tenant is integrated, and data initialization is performed on a SaaS database corresponding to a supplier platform; the existing supplier data of each tenant is collected and integrated, the database structure between the supplier platform and each tenant is synchronized by using an otter tool, and the integrated all the supplier data is brushed into the database of the supplier platform; the key data comprises supplier enterprise basic data, supplier service area data, supplier warehousing related data, supplier contact data, supplier account information data, and supplier user data; the supplier platform is a SaaS service platform connecting the service provider to be built subsequently; the business scene comprises a registration scene, an audit scene, a login scene, and an information management scene, and the number of the service providers is at least one; a database construction module configured to construct a SaaS database based on the business data and the business scene corresponding thereto; a data processing module configured to obtain target data from the SaaS database in response to a data obtaining request initiated by a tenant, and send the target data to the tenant; wherein the tenant refers to a user leasing a data storage space from a service provider, and the multi-tenancy comprises at least two tenants adopting different data storage modes; the database construction module is further configured to: obtain service provider information corresponding to the business data; construct a SaaS service platform connecting the service providers based on the service provider information, the business data, and the business scene corresponding thereto, the SaaS service platform comprising a message middleware and the SaaS database; The database construction module is further configured to: after the step of constructing the SaaS database based on the business data and the corresponding business scenarios, acquire interaction data between the multi-tenants and the corresponding service providers, update the business data according to the interaction data, and update the corresponding data in the SaaS database according to the updated business data; The database construction module is further configured to: monitor business nodes at which the multi-tenants and the service providers conduct business interactions; establish a business message queue for each business node; and send the interaction data generated at the business nodes to the business message queue and acquire the interaction data from the business message queue; The database construction module is further configured to: monitor a message log corresponding to the business message queue, determine whether the message log is an information sending failure log; if yes, store the interaction data indicated by the information sending failure log to the SaaS database; The database construction module is further configured to: set a scheduling period, and store the interaction data indicated by the information sending failure log to the SaaS database according to the scheduling period.

6. An electronic device, comprising: comprise: one or more processors; a storage device configured to store one or more programs, when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the method according to any one of claims 1-4.

7. A computer readable medium having stored thereon a computer program, characterized in that, The program is executed by the processor to implement the method according to any one of claims 1-4.

Images