Forward proxy method realized based on Kong gateway

Abstract

The invention discloses a forward proxy method realized based on a Kong gateway. The third party data API interface Consumer and the Kong API gateway are located in an intranet segment without publicnetwork access authority. a Forward _ Proxy plug-in is operated on the Kong API gateway; the Forward _ Proxy plug-in is connected with a third-party data API interface Upstream operating in a public network through a standard Proxy proxy server. The Kong gateway is provided with a Service routing strategy and a Route routing strategy, the function is provided by a Kong native source, a Forward _ Proxy plug-in is started for the Service, and the plug-in executes forward proxy forwarding logic and is realized by an LUA language. Unified address planning management can be carried out on a large number of third-party APIs, and the third-party APIs are output to a background application in a gateway service mode.

Description

Technical field [0001] The present invention relates to the field of computer technology, in particular to a forward proxy method based on Kong gateway. Background technique [0002] In the back-end technology of operating APP products, it is necessary to interface with the data API interfaces of many third-party suppliers, so that when the self-built data warehouse cannot meet the user's query request, the request will be distributed to the API interface of the partner. Users provide services. [0003] The initial technical implementation is to directly hard-code the third-party data interface address in various back-end application codes. The production environment application server directly communicates with the third-party API interface of the public network, and all machines in the production environment can communicate with the external network. To communicate. However, the existing technology has the following disadvantages: [0004] 1. High maintenance cost: [0005] With ...

AI Technical Summary

Problems solved by technology

As a result, the isolation of the internal and external networks in the production environment and the capacity planning of the network segment are not controlled by the operation and maintenance personnel, and the implementation logic of the application code needs to be reduced.

[0008] 2. The interaction between the background application and the third-party API occupies a network channel with the normal business request processing, and it is impossible to distinguish traffic, and it is impossible to upgrade targetedly

[0010] 1. The interaction between the background application and the third-party API occurs in many application servers, and the data distribution and diffusion of network bandwidth consumption, number of connections, delay, and interaction results make it difficult to conduct unified monitoring and management

[0011] 2. When the background application is deployed on the public cloud, because it needs to communicate with the public network, it is impossible to use a cheaper intranet cloud host, and must use a cloud host with external network bandwidth, which has high economic costs

[0012] 4. Performance issues

When interacting with third-party APIs, the operating system layer needs to complete a large number of third-party domain name resolutions, and because of the CDN and security policies of third-party APIs, it is impossible to reduce the cost of public network domain name resolution by establishing an internal DNS server

[0014] 2. Firewall resource consumption increases

A large number of application background servers frequently and actively initiate external TCP connection requests, which increases the overhead of firewall NAT address translation, security rule matching, packet filtering, and logging, and the CPU resource consumption of the firewall remains high.

Images