CN115065609A - B-end SaaS system hybrid deployment method and system - Google Patents
B-end SaaS system hybrid deployment method and system Download PDFInfo
- Publication number
- CN115065609A CN115065609A CN202210983946.9A CN202210983946A CN115065609A CN 115065609 A CN115065609 A CN 115065609A CN 202210983946 A CN202210983946 A CN 202210983946A CN 115065609 A CN115065609 A CN 115065609A
- Authority
- CN
- China
- Prior art keywords
- user operation
- operation request
- control layer
- routing control
- environment
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
- H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Telephonic Communication Services (AREA)
Abstract
The application relates to the technical field of computers, and particularly discloses a mixed deployment method and a mixed deployment system of a B-end SaaS (software as a service) system, wherein the mixed deployment method comprises the following steps: acquiring a user operation request, wherein the user operation request carries environment configuration information; sending the user operation request to a routing control layer; the routing control layer carries out request identification on the user operation request through the environment configuration information; the routing control layer sends the user operation request to a target environment; and the target environment sorts the target data according to the user operation request and returns the target data to the user. Whether the SaaS system is a cloud edition user or an independent deployment edition user, the routing control layer can forward the user operation request to the corresponding target environment, and simultaneously return the result of the user operation request to the user, so that access inlets do not need to be switched due to different versions, and the operation of the SaaS system is simplified.
Description
Technical Field
The embodiment of the application relates to the technical field of computers, in particular to a method and a system for mixed deployment of a B-terminal SaaS system.
Background
At present, most B-end SaaS systems are divided into a cloud version and an independent deployment version (or professional version). By cloud version is understood that all users share a huge set of servers, databases and network facilities. The independent deployment version is composed of independent domain names, servers, databases and network facilities. The cloud edition aims at small and medium-sized clients with small data volume, and can centralize server resources of a large number of small and medium-sized users. For large customers with large data volumes, independent deployment versions need to be used because the required resources are large.
Although the program codes of the cloud edition and the independent deployment edition are the same, the cloud edition and the independent deployment edition are respectively deployed in different network, server and database environments, so that different configuration files are required for management, and customers of the cloud edition and the independent deployment edition also need to access the SaaS system through different access portals (for example, a cloud disk domain name and an independent deployment edition domain name). If a cloud-version user grows into a large customer, server maintenance personnel are required to additionally set up an independent deployment environment and copy a database of the user to a new environment, and the customer needs to switch to a new domain name to use the service of the SaaS system.
Disclosure of Invention
The embodiment of the application provides a method and a system for mixed deployment of a B-side SaaS system, which can save the maintenance cost of the system while simplifying the operation of the SaaS system.
In a first aspect, an embodiment of the present application provides a B-side SaaS system hybrid deployment method, including:
acquiring a user operation request, wherein the user operation request carries environment configuration information, and the environment configuration information comprises a network environment, a server and a database;
sending the user operation request to a routing control layer;
the routing control layer carries out request identification on the user operation request through the environment configuration information;
the routing control layer sends the user operation request to a target environment;
and the target environment sorts the target data according to the user operation request and returns the target data to the user.
In the method for hybrid deployment of a B-side SaaS system provided in the embodiment of the present application, the target environment collates target data according to the user operation request and returns the target data to a user, including:
the target environment acquires target data according to the user operation request;
integrating the target data and the environment configuration information;
returning the integrated target data to the routing control layer;
and the routing control layer returns the target data to the user.
In the B-side SaaS system hybrid deployment method provided in the embodiment of the present application, returning the integrated target data to a user includes:
returning the target data to the routing control layer;
and the routing control layer returns the target data to the user.
In the B-side SaaS system hybrid deployment method provided in the embodiment of the present application, the sending, by the route control layer, the user operation request to a target environment includes:
if the user operation request is a first request, the routing control layer forwards the user operation request to a first environment;
and if the user operation request is a second request, the routing control layer forwards the user operation request to a second environment.
In the method for hybrid deployment of a B-side SaaS system provided in the embodiment of the present application, the performing, by the routing control layer, request identification on the user operation request through the environment configuration information includes:
the environment configuration information comprises a network environment, a server and a database;
the routing control layer identifies the network environment, the server, and the database, respectively.
In a second aspect, an embodiment of the present application provides a B-side SaaS system hybrid deployment apparatus, including:
the system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring a user operation request, the user operation request carries environment configuration information, and the environment configuration information comprises a network environment, a server and a database;
the first sending unit is used for sending the user operation request to a routing control layer;
the identification unit is used for the routing control layer to perform request identification on the user operation request through the environment configuration information;
a second sending unit, configured to send, by the routing control layer, the user operation request to a target environment;
and the returning unit is used for sorting the target data according to the user operation request and returning the target data to the user.
In the B-side SaaS system hybrid deployment apparatus provided in the embodiment of the present application, the return unit is configured to:
the target environment acquires target data according to the user operation request;
integrating the target data and the environment configuration information;
returning the integrated target data to the routing control layer;
and the routing control layer returns the target data to the user.
In the B-side SaaS system hybrid deployment apparatus provided in the embodiment of the present application, the return unit is further configured to:
returning the target data to the routing control layer;
and the routing control layer returns the target data to the user.
In a third aspect, an embodiment of the present application provides a storage medium, where the storage medium stores a plurality of instructions, and the instructions are suitable for a processor to load and execute steps in any one of the methods for hybrid deployment of a B-side SaaS system provided in the embodiments of the present application.
In a fourth aspect, an embodiment of the present application provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor executes the computer program to implement the steps in the method for hybrid deployment of a B-end SaaS system according to any one of the embodiments of the present application.
To sum up, the method for hybrid deployment of a B-side SaaS system provided by the embodiment of the present application includes: acquiring a user operation request, wherein the user operation request carries environment configuration information; sending the user operation request to a routing control layer; the routing control layer carries out request identification on the user operation request through the environment configuration information; the routing control layer sends the user operation request to a target environment; and the target environment sorts the target data according to the user operation request and returns the target data to the user. Whether the SaaS system is a cloud edition user or an independent deployment edition user, the routing control layer can forward the user operation request to the corresponding target environment, and simultaneously return the result of the user operation request to the user, so that access inlets do not need to be switched due to different versions, and the operation of the SaaS system is simplified.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a scene schematic diagram of a B-end SaaS system hybrid deployment system according to an embodiment of the present application.
Fig. 2 is a flowchart illustrating a B-side SaaS system hybrid deployment method according to an embodiment of the present disclosure.
Fig. 3 is a schematic structural diagram of a B-side SaaS system hybrid deployment apparatus according to an embodiment of the present application.
Fig. 4 is a schematic structural diagram of a server 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
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The terms "first" and "second", etc. in this application are used to distinguish between different objects and not to describe a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or modules is not limited to the listed steps or modules but may alternatively include other steps or modules not listed or inherent to such process, method, article, or apparatus.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
The embodiment of the application provides a method and a system for mixed deployment of a B-terminal SaaS system. Referring to fig. 1, fig. 1 is a scene schematic diagram of a B-side SaaS system hybrid deployment system according to an embodiment of the present application.
In the embodiment of the application, the user operation request can come from a cloud edition and/or a plurality of independent deployment editions, wherein the user operation request carries environment configuration information corresponding to the user operation request, the environment configuration information comprises network, server and database environments corresponding to different editions, the routing control layer receives the user operation request, identifies the edition information of the user operation request according to the environment configuration information, and sends the user operation request to the corresponding edition.
It should be noted that the scene schematic diagram of the B-side SaaS system hybrid deployment system shown in fig. 1 is merely an example, and the SaaS system and the scene described in the embodiment of the present application are used to more clearly illustrate the technical solution in the embodiment of the present application, and do not limit the technical solution provided in the embodiment of the present application.
Referring to fig. 2, fig. 2 is a schematic flow chart of a B-side SaaS system hybrid deployment method provided in an embodiment of the present application, where a specific flow of the B-side SaaS system hybrid deployment method may be as follows:
101. the method comprises the steps of obtaining a user operation request, wherein the user operation request carries environment configuration information, and the environment configuration information comprises a network environment, a server and a database.
In some embodiments, the cloud version and the independent deployment version are respectively deployed in different network environments, servers and databases and managed by different configuration files, and a user needs to access the SaaS system through different access portals (for example, a cloud disk domain name and an independent deployment version domain name) of the cloud version and the independent deployment version.
102. And sending the user operation request to a routing control layer.
103. And the routing control layer carries out request identification on the user operation request through the environment configuration information.
In some embodiments, this step 103 may include: the routing control layer identifies the network environment, the server and the database, respectively.
104. And the routing control layer sends the user operation request to the target environment.
In some embodiments, this step 104 may include:
if the user operation request is a first request, the routing control layer forwards the user operation request to a first environment;
and if the user operation request is a second request, the routing control layer forwards the user operation request to a second environment.
Specifically, the first request is a request sent by a cloud edition user, and the routing control layer forwards the request sent by the cloud edition user to an environment corresponding to environment configuration information carried by the first request; the second request is a request sent by the independent deployment version user, and the routing control layer forwards the request sent by the independent deployment version user to an environment corresponding to the environment configuration information carried by the second request.
105. And the target environment sorts the target data according to the user operation request and returns the target data to the user.
In some embodiments, this step 105 may include:
the target environment acquires target data according to the user operation request;
integrating the target data and the environment configuration information;
returning the integrated target data to the routing control layer;
the routing control layer returns the target data to the user.
The returning of the integrated target data to the user may include:
returning the target data to the routing control layer;
the routing control layer returns the target data to the user.
In some embodiments, different user operation requests may correspond to different versions, and therefore, it is necessary to obtain target data in a corresponding target environment, and integrate environment configuration information of the user operation request into the target data, so that the routing control layer conveniently returns the obtained target data to a user corresponding to the user operation request.
All the above technical solutions may be combined arbitrarily to form an optional embodiment of the present application, and are not described in detail herein.
To sum up, the method for hybrid deployment of a B-side SaaS system provided by the embodiment of the present application includes: acquiring a user operation request, wherein the user operation request carries environment configuration information; sending the user operation request to a routing control layer; the routing control layer carries out request identification on the user operation request through the environment configuration information; the routing control layer sends the user operation request to a target environment; and the target environment sorts the target data according to the user operation request and returns the target data to the user. Whether the users are cloud edition users or independently deployed edition users, the routing control layer can forward the user operation requests to the corresponding target environments, meanwhile, the results of the user operation requests are returned to the users, access inlets do not need to be switched due to different editions, and the operation of the SaaS system is simplified.
An embodiment of the present application further provides a B-side SaaS system hybrid deployment apparatus, as shown in fig. 3, fig. 3 is a schematic structural diagram of the B-side SaaS system hybrid deployment apparatus provided in the embodiment of the present application. The B-side SaaS system hybrid deployment apparatus 300 includes an obtaining unit 301, a first sending unit 302, an identifying unit 303, a second sending unit 304, and a returning unit 305. Wherein, the first and the second end of the pipe are connected with each other,
an obtaining unit 301, configured to obtain a user operation request, where the user operation request carries environment configuration information, the environment configuration information includes a network environment, a server, and a database, and is used to obtain the user operation request, the user operation request carries environment configuration information, and the environment configuration information includes the network environment, the server, and the database.
A first sending unit 302, configured to send the user operation request to the routing control layer;
an identifying unit 303, configured to perform request identification on the user operation request through the environment configuration information by the routing control layer;
a second sending unit 304, configured to send the user operation request to the target environment by the routing control layer;
a returning unit 305, configured to sort the target data according to the user operation request, and return the target data to the user.
In some embodiments, the return unit 305 may specifically be configured to:
the target environment acquires target data according to the user operation request;
integrating the target data and the environment configuration information;
returning the integrated target data to the routing control layer;
the routing control layer returns the target data to the user.
All the above technical solutions can be combined arbitrarily to form the optional embodiments of the present application, and are not described herein again.
The meaning of the noun is the same as that in the above-mentioned B-terminal SaaS system hybrid deployment method, and specific implementation details may refer to the description in the method embodiment.
The B-side SaaS system hybrid deployment apparatus 300 provided in the embodiment of the present application acquires a user operation request through the acquisition unit 301, where the user operation request carries environment configuration information, the environment configuration information includes a network environment, a server, and a database, and is used to acquire the user operation request, the user operation request carries environment configuration information, and the environment configuration information includes the network environment, the server, and the database; the first sending unit 302 sends the user operation request to the routing control layer; the identification unit 303 is configured to perform request identification on the user operation request through the environment configuration information by the routing control layer; a second sending unit 304, configured to send the user operation request to the target environment by the routing control layer; a returning unit 305, configured to sort the target data according to the user operation request, and return the target data to the user. The device simplifies the operation of the SaaS system.
The embodiment of the present application further provides a server, as shown in fig. 4, which shows a schematic structural diagram of the server according to the embodiment of the present application, specifically:
the server may include components such as a processor 401 of one or more processing cores, memory 402 of one or more computer-readable storage media, a power supply 403, and an input unit 404. Those skilled in the art will appreciate that the server architecture shown in FIG. 4 is not meant to be limiting, and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components. Wherein:
the processor 401 is a control center of the server, connects various parts of the entire server using various interfaces and lines, and performs various functions of the server and processes data by running or executing software programs and/or modules stored in the memory 402 and calling data stored in the memory 402, thereby performing overall monitoring of the server. Optionally, processor 401 may include one or more processing cores; preferably, the processor 401 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 401.
The memory 402 may be used to store software programs and modules, and the processor 401 executes various functional applications and data processing by operating the software programs and modules stored in the memory 402. The memory 402 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data created according to the use of the server, and the like. Further, the memory 402 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. Accordingly, the memory 402 may also include a memory controller to provide the processor 401 access to the memory 402.
The server further includes a power supply 403 for supplying power to each component, and preferably, the power supply 403 may be logically connected to the processor 401 through a power management system, so as to implement functions of managing charging, discharging, and power consumption through the power management system. The power supply 403 may also include any component of one or more dc or ac power sources, recharging systems, power failure detection circuitry, power converters or inverters, power status indicators, and the like.
The server may also include an input unit 404, the input unit 404 being operable to receive input numeric or character information and to generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.
Although not shown, the server may further include a display unit and the like, which will not be described in detail herein. Specifically, in this embodiment, the processor 401 in the server loads the executable file corresponding to the process of one or more application programs into the memory 402 according to the following instructions, and the processor 401 runs the application program stored in the memory 402, thereby implementing various functions as follows:
acquiring a user operation request, wherein the user operation request carries environment configuration information, and the environment configuration information comprises a network environment, a server and a database; sending the user operation request to a routing control layer; the routing control layer carries out request identification on the user operation request through the environment configuration information; the routing control layer sends the user operation request to a target environment; and the target environment sorts the target data according to the user operation request and returns the target data to the user.
The above operations can be specifically referred to the previous embodiments, and are not described herein.
Accordingly, an electronic device may include, as shown in fig. 5, a Radio Frequency (RF) circuit 501, a memory 402 including one or more computer-readable storage media, an input unit 404, a display unit 504, a sensor 505, an audio circuit 506, a Wireless Fidelity (WiFi) module 507, a processor 401 including one or more processing cores, and a power supply 403. Those skilled in the art will appreciate that the electronic device configuration shown in fig. 5 does not constitute a limitation of the electronic device and may include more or fewer components than shown, or some components may be combined, or a different arrangement of components. Wherein:
the RF circuit 501 may be used for receiving and transmitting signals during a message transmission or communication process, and in particular, for receiving downlink information of a base station and then sending the received downlink information to the one or more processors 401; in addition, data relating to uplink is transmitted to the base station. In general, RF circuit 501 includes, but is not limited to, an antenna, at least one Amplifier, a tuner, one or more oscillators, a Subscriber Identity Module (SIM) card, a transceiver, a coupler, a Low Noise Amplifier (LNA), a duplexer, and the like. In addition, the RF circuitry 501 may also communicate with networks and other devices via wireless communications. The wireless communication may use any communication standard or protocol, including but not limited to Global System for Mobile communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), email, Short Message Service (SMS), and the like.
The memory 402 may be used to store software programs and modules, and the processor 401 executes various functional applications and data processing by operating the software programs and modules stored in the memory 402. The memory 402 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phone book, etc.) created according to the use of the electronic device, and the like. Further, the memory 402 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. Accordingly, the memory 402 may also include a memory controller to provide the processor 401 and the input unit 404 access to the memory 402.
The input unit 404 may be used to receive input numeric or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control. Specifically, in one particular embodiment, input unit 404 may include a touch-sensitive surface as well as other input devices. The touch-sensitive surface, also referred to as a touch display screen or a touch pad, may collect touch operations by a user (e.g., operations by a user on or near the touch-sensitive surface using a finger, a stylus, or any other suitable object or attachment) thereon or nearby, and drive the corresponding connection device according to a predetermined program. Alternatively, the touch sensitive surface may comprise two parts, a touch detection means and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 401, and can receive and execute commands sent by the processor 401. In addition, the touch sensitive surface can be implemented in various types, such as resistive, capacitive, infrared, and surface acoustic wave. The input unit 404 may include other input devices in addition to a touch-sensitive surface. In particular, other input devices may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like.
The display unit 504 may be used to display information input by or provided to a user and various graphical user interfaces of the electronic device, which may be made up of graphics, text, icons, video, and any combination thereof. The Display unit 504 may include a Display panel, and optionally, the Display panel may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like. Further, the touch-sensitive surface may overlay the display panel, and when a touch operation is detected on or near the touch-sensitive surface, the touch operation is transmitted to the processor 401 to determine the type of the touch event, and then the processor 401 provides a corresponding visual output on the display panel according to the type of the touch event. Although in FIG. 5 the touch sensitive surface and the display panel are implemented as two separate components for input and output functions, in some embodiments the touch sensitive surface may be integrated with the display panel for input and output functions.
The electronic device may also include at least one sensor 505, such as light sensors, motion sensors, and other sensors. In particular, the light sensor may include an ambient light sensor that may adjust the brightness of the display panel according to the brightness of ambient light, and a proximity sensor that may turn off the display panel and/or the backlight when the electronic device is moved to the ear. As one of the motion sensors, the gravitational acceleration sensor may detect the magnitude of acceleration in each direction (generally three axes), detect the magnitude and direction of gravity when stationary, and may be used for applications of identifying gestures of a mobile phone (such as horizontal and vertical screen switching, related games, magnetometer gesture calibration), vibration identification related functions (such as pedometer and tapping), and other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which may also be configured for the electronic device, and are not described herein again.
WiFi belongs to short-distance wireless transmission technology, and the electronic equipment can help a user to receive and send emails, browse webpages, access streaming media and the like through the WiFi module 507, and provides wireless broadband internet access for the user. Although fig. 5 shows the WiFi module 507, it is understood that it does not belong to the essential constitution of the electronic device, and may be omitted entirely as needed within the scope not changing the essence of the invention.
The processor 401 is a control center of the electronic device, connects various parts of the entire mobile phone by using various interfaces and lines, and performs various functions of the electronic device and processes data by operating or executing software programs and/or modules stored in the memory 402 and calling data stored in the memory 402, thereby integrally monitoring the mobile phone. Optionally, processor 401 may include one or more processing cores; preferably, the processor 401 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 401.
The electronic device also includes a power supply 403 (e.g., a battery) for powering the various components, which may preferably be logically coupled to the processor 401 via a power management system to manage charging, discharging, and power consumption management functions via the power management system. The power supply 403 may also include any component of one or more dc or ac power sources, recharging systems, power failure detection circuitry, power converters or inverters, power status indicators, and the like.
Although not shown, the electronic device may further include a camera, a bluetooth module, and the like, which are not described in detail herein. Specifically, in this embodiment, the processor 401 in the electronic device loads the executable file corresponding to the process of one or more application programs into the memory 402 according to the following instructions, and the processor 401 runs the application program stored in the memory 402, thereby implementing various functions:
acquiring a user operation request, wherein the user operation request carries environment configuration information, and the environment configuration information comprises a network environment, a server and a database; sending the user operation request to a routing control layer; the routing control layer carries out request identification on the user operation request through the environment configuration information; the routing control layer sends the user operation request to a target environment; and the target environment sorts the target data according to the user operation request and returns the target data to the user.
The above operations can be specifically referred to the previous embodiments, and are not described herein.
It will be understood by those skilled in the art that all or part of the steps of the methods of the above embodiments may be performed by instructions or by associated hardware controlled by the instructions, which may be stored in a computer readable storage medium and loaded and executed by a processor.
To this end, an embodiment of the present application provides a storage medium, where a plurality of instructions are stored, and the instructions can be loaded by a processor to execute steps in any one of the methods for hybrid deployment of a B-side SaaS system provided in the embodiment of the present application. For example, the instructions may perform the steps of:
acquiring a user operation request, wherein the user operation request carries environment configuration information, and the environment configuration information comprises a network environment, a server and a database; sending the user operation request to a routing control layer; the routing control layer carries out request identification on the user operation request through the environment configuration information; the routing control layer sends the user operation request to a target environment; and the target environment sorts the target data according to the user operation request and returns the target data to the user.
The above operations can be implemented in the foregoing embodiments, and are not described in detail herein.
Wherein the storage medium may include: read Only Memory (ROM), Random Access Memory (RAM), magnetic or optical disks, and the like.
Since the instructions stored in the storage medium may execute the steps in any B-side SaaS system hybrid deployment method provided in the embodiment of the present application, beneficial effects that can be achieved by any B-side SaaS system hybrid deployment method provided in the embodiment of the present application may be achieved, which are detailed in the foregoing embodiments and are not described herein again.
The method and the system for mixed deployment of the B-side SaaS system provided by the embodiment of the present application are described in detail above, a specific example is applied in the description to explain the principle and the implementation manner of the present application, and the description of the above embodiment is only used to help understanding the method and the core idea of the present application; meanwhile, for those skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (10)
1. A mixed deployment method of a B-end SaaS system is characterized by comprising the following steps:
acquiring a user operation request, wherein the user operation request carries environment configuration information, and the environment configuration information comprises a network environment, a server and a database;
sending the user operation request to a routing control layer;
the routing control layer carries out request identification on the user operation request through the environment configuration information;
the routing control layer sends the user operation request to a target environment;
and the target environment sorts the target data according to the user operation request and returns the target data to the user.
2. The B-side SaaS system hybrid deployment method of claim 1, wherein the target environment sorts target data according to the user operation request and returns the target data to a user, comprising:
the target environment acquires target data according to the user operation request;
integrating the target data and the environment configuration information;
returning the integrated target data to the routing control layer;
and the routing control layer returns the target data to the user.
3. The B-side SaaS system hybrid deployment method of claim 2, wherein returning the integrated target data to a user comprises:
returning the target data to the routing control layer;
and the routing control layer returns the target data to the user.
4. The B-side SaaS system hybrid deployment method of claim 1, wherein the routing control layer sends the user operation request to a target environment, comprising:
if the user operation request is a first request, the routing control layer forwards the user operation request to a first environment;
and if the user operation request is a second request, the routing control layer forwards the user operation request to a second environment.
5. The B-side SaaS system hybrid deployment method of claim 1, wherein the route control layer performs request identification on the user operation request through the environment configuration information, and the method comprises:
the environment configuration information comprises a network environment, a server and a database;
the routing control layer identifies the network environment, the server, and the database, respectively.
6. A B-end SaaS system hybrid deployment device is characterized by comprising:
the system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring a user operation request, the user operation request carries environment configuration information, and the environment configuration information comprises a network environment, a server and a database;
the first sending unit is used for sending the user operation request to a routing control layer;
the identification unit is used for the routing control layer to perform request identification on the user operation request through the environment configuration information;
a second sending unit, configured to send, by the routing control layer, the user operation request to a target environment;
and the returning unit is used for sorting the target data according to the user operation request and returning the target data to the user.
7. The B-side SaaS system hybrid deployment apparatus of claim 6, wherein the return unit is configured to:
the target environment acquires target data according to the user operation request;
integrating the target data and the environment configuration information;
returning the integrated target data to the routing control layer;
and the routing control layer returns the target data to the user.
8. The B-side SaaS system hybrid deployment apparatus of claim 7, wherein the return unit is further configured to:
returning the target data to the routing control layer;
and the routing control layer returns the target data to the user.
9. A storage medium, characterized in that the storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor to execute the B-side SaaS system hybrid deployment method according to any one of claims 1 to 5.
10. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the B-side SaaS system hybrid deployment method according to any one of claims 1 to 5 when executing the computer program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210983946.9A CN115065609A (en) | 2022-08-17 | 2022-08-17 | B-end SaaS system hybrid deployment method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210983946.9A CN115065609A (en) | 2022-08-17 | 2022-08-17 | B-end SaaS system hybrid deployment method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115065609A true CN115065609A (en) | 2022-09-16 |
Family
ID=83208285
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210983946.9A Pending CN115065609A (en) | 2022-08-17 | 2022-08-17 | B-end SaaS system hybrid deployment method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115065609A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115344791A (en) * | 2022-10-20 | 2022-11-15 | 深圳美云集网络科技有限责任公司 | Batch cost query method based on cross-border e-commerce and related device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104426868A (en) * | 2013-08-28 | 2015-03-18 | 腾讯科技（深圳）有限公司 | Request processing method and processing apparatus |
| CN111913870A (en) * | 2019-05-09 | 2020-11-10 | 腾讯科技（深圳）有限公司 | Multi-environment management method, device, system, equipment and medium |
| CN112181438A (en) * | 2020-09-18 | 2021-01-05 | 杭州卓健信息科技有限公司 | Micro-service independent deployment system and method in 2B SAAS platform |
| CN114756250A (en) * | 2022-04-12 | 2022-07-15 | 特赞（上海）信息科技有限公司 | Hybrid cloud deployment system and method of saas system, electronic device and medium |
-
2022
- 2022-08-17 CN CN202210983946.9A patent/CN115065609A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104426868A (en) * | 2013-08-28 | 2015-03-18 | 腾讯科技（深圳）有限公司 | Request processing method and processing apparatus |
| CN111913870A (en) * | 2019-05-09 | 2020-11-10 | 腾讯科技（深圳）有限公司 | Multi-environment management method, device, system, equipment and medium |
| CN112181438A (en) * | 2020-09-18 | 2021-01-05 | 杭州卓健信息科技有限公司 | Micro-service independent deployment system and method in 2B SAAS platform |
| CN114756250A (en) * | 2022-04-12 | 2022-07-15 | 特赞（上海）信息科技有限公司 | Hybrid cloud deployment system and method of saas system, electronic device and medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115344791A (en) * | 2022-10-20 | 2022-11-15 | 深圳美云集网络科技有限责任公司 | Batch cost query method based on cross-border e-commerce and related device |
| CN115344791B (en) * | 2022-10-20 | 2022-12-13 | 深圳美云集网络科技有限责任公司 | Batch cost query method based on cross-border e-commerce and related device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104518953B (en) | Method for deleting message, instant communication terminal and system | |
| CN108667884B (en) | Mirror image distribution method, mirror image acquisition method and device | |
| CN109062467B (en) | Split screen application switching method and device, storage medium and electronic equipment | |
| CN105471931B (en) | Method, device and system for inquiring service data | |
| US20170316781A1 (en) | Remote electronic service requesting and processing method, server, and terminal | |
| CN106502703B (en) | Function calling method and device | |
| CN106775833B (en) | Device driver loading method, terminal and system | |
| CN108039963B (en) | Container configuration method and device and storage medium | |
| CN106953898B (en) | Method and device for acquiring software package | |
| US10298590B2 (en) | Application-based service providing method, apparatus, and system | |
| CN108809805B (en) | Information interaction method and system and public account client | |
| CN106682189B (en) | File name display method and device | |
| CN106095423B (en) | Method, terminal and server for providing browsing service | |
| CN109688611B (en) | Frequency band parameter configuration method, device, terminal and storage medium | |
| CN112749074A (en) | Test case recommendation method and device | |
| CN105631059B (en) | Data processing method, data processing device and data processing system | |
| CN115065609A (en) | B-end SaaS system hybrid deployment method and system | |
| CN106303616B (en) | Play control method, device and terminal | |
| CN107766351B (en) | File directory identification method and device | |
| CN111274463A (en) | Information display method and device based on IM contact person grouping setting and storage medium | |
| CN110196662B (en) | Method, device, terminal and storage medium for displaying synchronization state | |
| WO2015067206A1 (en) | File searching method and terminal | |
| CN106933626B (en) | Application association method and device | |
| CN108234275B (en) | Method and device for releasing communication information | |
| CN106657281B (en) | File sharing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20220916 |