Containerized service method and system

Abstract

A containerized service system, upon receiving a frontend connection request, determines whether the request originates from a management terminal. If the determination is affirmative, the frontend server generates and transmits a verification backend connection request indicating internal verification to a backend server. The backend server then schedules a set of verification containers through the container platform to perform internal verification based on the verification backend connection request. If the determination is negative, the frontend server generates and transmits a service backend connection request without indicating internal verification to the backend server. The backend server then schedules a set of service containers corresponding to the service backend connection request through the container platform to provide external service.

Description

Technical Field

[0001] This invention relates to a service method, and more particularly to a containerized service method and system. Prior Technology

[0002] Most existing online banks adopt a front-end / back-end separation architecture. The front-end typically uses Vue.js as the development framework, responsible for UI rendering and business logic processing. Front-end resources are served by asynchronous web servers (such as Nginx), which are responsible for delivering compiled static resources. Back-end services commonly use Java as the development language, and the back-end application programming interface (API) is deployed on a multi-cloud or hybrid cloud platform (such as Anthos). External access is achieved through Anthos's traffic distribution (Ingress) or service functions.

[0003] During service deployment, the front-end can prevent customers from connecting to the new service by disabling load balancing solutions (such as F5), and can directly deploy the new service on the web server for testing within the internal environment. This allows the front-end to verify the service's correctness beforehand, ensuring stable operation after official launch and preventing customers from encountering anomalies when accessing it from the outside.

[0004] However, as backend services shift to containerized microservice architectures, this verification process becomes more complex. In microservice architectures, each service typically runs independently as a container, making it impossible to rely solely on traditional load balancing tools like F5 for internal testing and verification. Furthermore, simply shutting down external traffic for internal verification increases the risk of anomalies occurring after a new service is deployed. Summary of the Invention

[0005] Therefore, the object of the present invention is to provide a containerized service method to solve the above-mentioned problems.

[0006] Therefore, the containerized service method of the present invention is implemented by a system including a front-end server and a back-end server. The front-end server is connected to a user terminal via an external network and to a management terminal and the back-end server via an internal network. The back-end server stores a container platform. The method includes a step (A), a step (B), and a step (C).

[0007] In step (A), when a front-end connection request is received, the front-end server determines whether the front-end connection request comes from the management terminal.

[0008] In step (B), when it is determined that the front-end connection request comes from the management terminal, the front-end server generates and sends a verification back-end connection request indicating internal verification to the back-end server, so that the back-end server schedules a set of verification containers through the container platform to perform internal verification based on the verification back-end connection request.

[0009] In step (C), when it is determined that the front-end connection request does not originate from the management terminal, the front-end server generates and transmits a service back-end connection request that does not indicate internal verification to the back-end server, so that the back-end server schedules a set of service containers corresponding to the service back-end connection request through the container platform to provide external services.

[0010] The purpose of this invention is to provide a containerized service system that solves the above-mentioned problems.

[0011] Therefore, the containerized service system of the present invention includes a backend server and a frontend server.

[0012] The backend server stores a container platform.

[0013] The front-end server is connected to a user terminal via an external network and to a management terminal and the back-end server via an internal network.

[0014] When a front-end connection request is received, the front-end server determines whether the front-end connection request comes from the management terminal.

[0015] When it is determined that the front-end connection request comes from the management terminal, the front-end server generates and sends a verification back-end connection request indicating that internal verification is to be performed to the back-end server, so that the back-end server schedules a set of verification containers through the container platform to perform internal verification based on the verification back-end connection request.

[0016] When it is determined that the front-end connection request does not originate from the management terminal, the front-end server generates and transmits a service back-end connection request that does not specify internal verification to the back-end server. As a result, the back-end server schedules a set of service containers corresponding to the service back-end connection request through the container platform to provide external services.

[0017] The advantages of this invention are: by having the front-end server generate the verification back-end connection request based on the front-end connection request from the management terminal, the back-end server is guided to perform internal verification; and by having the front-end server generate the service back-end connection request based on the front-end connection request not from the management terminal, the back-end server is guided to provide external services, thereby significantly reducing the occurrence of abnormal external services after going online. Simple Explanation of the Diagram

[0018] Other features and effects of the present invention will be clearly presented in the embodiments with reference to the drawings, wherein: Figure 1 is a block diagram illustrating an embodiment of the containerized service system of the present invention; and Figure 2 is a flowchart illustrating an embodiment of the containerized service method of the present invention. Implementation

[0019] Before the invention is described in detail, it should be noted that similar elements are represented by the same numbers in the following description.

[0020] Referring to Figure 1, an embodiment of the containerized service system 1 of the present invention includes a backend server 11 and a frontend server 12.

[0021] The backend server 11 stores a container platform. The backend server 11 is, for example, an application server, but is not limited thereto.

[0022] The front-end server 12 connects to a user terminal 21 via an external network 101 and to a management terminal 22 and the back-end server 11 via an internal network 102. The front-end server 12 may connect directly to the management terminal 22 via the internal network 102, and connect to the back-end server 11 via an ingress gateway through the internal network 102. The external network 101 may be, for example, the internet, and the internal network 102 may be, for example, an intranet. The front-end server 12 may be, for example, a web server, the user terminal 21 may be, for example, an electronic device used by a user browsing a webpage, and the management terminal 22 may be, for example, an electronic device used by an internal administrator, but is not limited thereto.

[0023] Referring to Figures 1 and 2, an embodiment of the containerized service method of the present invention is shown to illustrate the operational details of the containerized service system 1 of the present invention.

[0024] In step 301, the front-end server 12 receives a front-end connection request.

[0025] In step 302, the front-end server 12 determines whether the front-end connection request originates from the management terminal 22. If it is determined that the front-end connection request originates from the management terminal 22, the process proceeds to step 303; if it is determined that the front-end connection request does not originate from the management terminal 22, it indicates that the front-end connection request originates from the external network 101, such as from the user terminal 21, and the process proceeds to step 304.

[0026] It is worth noting that in this embodiment, the front-end connection request includes a domain name. The front-end server 12 determines whether the front-end connection request originates from the management terminal 22 based on the domain name in the front-end connection request. Since the implementation method of determining whether the front-end connection request originates from the management terminal 22 using the domain name is well known to those skilled in the art, a detailed explanation is omitted here for the sake of brevity. In other embodiments, the front-end server 12 may also determine whether the front-end connection request originates from the management terminal 22 based on, for example, an IP address included in the front-end connection request, but this is not a limitation.

[0027] In step 303, the front-end server 12 generates and transmits a verification back-end connection request indicating internal verification to the back-end server 11.

[0028] In step 304, the front-end server 12 generates and transmits a service back-end connection request that does not indicate internal authentication to the back-end server 11.

[0029] It is worth noting that, in this embodiment, when it is determined that the front-end connection request comes from the management terminal 22, the verification back-end connection request generated by the front-end server 12 has a header with a specific string to indicate that internal verification is to be performed. The specific string is, for example, "stage". When it is determined that the front-end connection request does not come from the management terminal 22, the service back-end connection request generated by the front-end server 12 does not have the specific string, that is, it does not indicate that internal verification is to be performed, but this is not a limitation.

[0030] In step 305, the backend server 11 receives a backend connection request to be executed.

[0031] In step 306, the backend server 11 determines whether the backend connection request to be executed indicates internal verification. If it is determined that the backend connection request to be executed indicates internal verification, that is, the backend connection request to be executed is the verification backend connection request, the process proceeds to step 307; if it is determined that the backend connection request to be executed does not indicate internal verification, that is, the backend connection request to be executed is the service backend connection request, the process proceeds to step 308.

[0032] It is worth noting that in this embodiment, the backend server 11 determines whether the header of the backend connection request to be executed has the specific string in order to determine whether the backend connection request to be executed indicates internal verification, but is not limited thereto.

[0033] In step 307, the backend server 11 schedules a set of verification containers (Pods) in a staged environment through the container platform for internal verification.

[0034] In step 308, the backend server 11 schedules a set of service containers corresponding to the backend connection requests to be executed in a production environment through the container platform to provide external services.

[0035] It is worth noting that, in this embodiment, the container platform utilizes the functions in the open-source service mesh, such as the virtual services and destination rules functions in Istio, to schedule the set of verification containers to direct internal verification services, or to schedule the set of service containers to direct external operational services, but is not limited thereto.

[0036] In summary, the containerized service method and system of the present invention, by having the front-end server 12 generate the verification back-end connection request based on the front-end connection request from the management terminal 22 to guide the back-end server 11 to perform internal verification, and by having the front-end server 12 generate the service back-end connection request based on the front-end connection request not from the management terminal 22 to guide the back-end server 11 to provide external services, significantly reduces the occurrence of abnormal external services after going live, thus effectively achieving the purpose of the present invention.

[0037] However, the above description is merely an embodiment of the present invention and should not be construed as limiting the scope of the present invention. Any simple equivalent changes and modifications made in accordance with the scope of the patent application and the contents of the patent specification of the present invention shall still fall within the scope of the patent of the present invention.

[0038] 1: Containerized service system 11: Backend Server 12: Front-end server 101: External Network 102: Internal Network 21: User Terminal 22: Management Terminal 301~308: Steps

Claims

1. A containerized service method, implemented by a system including a front-end server and a back-end server, the front-end server being connected to an external network and an internal network, and connected to a management terminal and the back-end server via the internal network, the back-end server storing a container platform, the method comprising the following steps: (A) when a front-end connection request is received, the front-end server determines whether the front-end connection request originates from the management terminal; (B) When it is determined that the front-end connection request originates from the management terminal, the front-end server generates and transmits an authentication back-end connection request indicating internal authentication to the back-end server, so that the back-end server schedules an authentication container set through the container platform to perform internal authentication based on the authentication back-end connection request; and (C) When it is determined that the front-end connection request does not originate from the management terminal, the front-end server generates and transmits a service back-end connection request that does not indicate internal authentication to the back-end server, so that the back-end server schedules a service container set corresponding to the service back-end connection request through the container platform to provide external services based on the service back-end connection request.

2. The containerized service method as described in request item 1, wherein, In step (A), the front-end connection request includes a domain name, and the front-end server determines whether the front-end connection request comes from the management terminal based on the domain name in the front-end connection request.

3. The containerized service method as described in request item 1, wherein, In step (B), the verification backend connection request includes a header with a specific string.

4. The containerized service method as described in request item 1, wherein, In step (B), the backend server schedules the set of verification containers in a prepared environment.

5. The containerized service method as described in request item 1, wherein, In step (C), the backend server schedules the service container set in a production environment.

6. A containerized service system, comprising: a backend server storing a container platform; and a frontend server connected to an external network and an internal network, and connected to a management terminal and the backend server via the internal network; wherein, When a front-end connection request is received, the front-end server determines whether the front-end connection request originates from the management terminal. If it does, the front-end server generates and sends a verification back-end connection request indicating internal verification to the back-end server. The back-end server then schedules a set of verification containers through the container platform to perform internal verification based on the verification back-end connection request. If it does not, the front-end server generates and sends a service back-end connection request that does not indicate internal verification to the back-end server. The back-end server then schedules a set of service containers corresponding to the service back-end connection request through the container platform to provide external services based on the service back-end connection request.

7. The containerized service system as described in claim 6, wherein, The front-end connection request includes a domain name. The front-end server determines that the front-end connection request comes from the management terminal based on the domain name in the front-end connection request.

8. The containerized service system as described in claim 6, wherein, The verification backend connection request includes a header with a specific string.

9. The containerized service system as described in claim 6, wherein, The backend server schedules the set of verification containers in a preparatory environment.

10. The containerized service system as described in claim 6, wherein, The backend server schedules the service container set in a production environment.

Images