Recent work needs, coupled with the relatively lack of domestic articles (search for the two articles), and the official documents in some of the demo also have some outdated places, so pen record these, hoping to help.
Let's introduce the next Kong (main reference website):
Official site: https://getkong.org
Official description: Kong is a scalable, open source API Layer (also known as an API Gateway, or API middleware). Kong runs in front of no RESTful API and is extended through Plugins, which provide extra functionality and services Beyo nd the core platform.
Kong is an extensible, open-source API layer that runs on a restful front end that can be extended via plugins (authentication, security, traffic control, analysis & monitoring, conversion, logging)
Before using Kong, the internal API architecture
1. Generic modules are not reused in each API
2. Difficult to maintain
3. Does not affect the other service state difficult to expand
4. Due to system restrictions on inefficient production
API architecture using the Kong post
1.Kong Unified Management Universal Plug-in
2. Efficient and scalable distributed architecture system3. Complete the extension with simple commands4. Team focus on business, Kong to deal with REST
API Gateway Kong Series (i) Primary knowledge