English | 简体中文
- latest QQ group: 512164278
A Managerment API Gateway in Java. Fizz Gateway is a Java-based microservice gateway that can realize hot service aggregation, automatic authorization selection, online service script coding, online testing, high-performance routing, API audit management and other purposes. It has a powerful The custom plug-in system can be extended by youself, and provides a friendly graphical configuration interface, which can quickly help enterprises to manage API services, reduce middle layer glue code, reduce coding investment, and improve the stability and security of API services.
account/password:admin
/Aa123!
health checking url:http://demo.fizzgate.com/admin/health
API access:http://demo.fizzgate.com/proxy/[Service Name]/[API Path]
- Cluster management: Fizz gateway nodes are stateless with configuration information that is automatically synchronized, and horizontal expansion of nodes and multi-cluster deployment are supported.
- Service aggregation: support hot http/dubbo/grpc service aggregation capabilities, support front-end and back-end coding, and update API anytime and anywhere.
- Load balancing: support round-robin load balancing.
- Service discovery: supports discovery of back-end servers from the Eureka registry.
- Configuration center: support access to apollo configuration center.
- HTTP reverse proxy: hide the real back-end services and support Rest API reverse proxy.
- Access strategy: support different strategies to access different APIs, configure different authentication, etc.
- IP black and white list: support the configuration of IP black and white list.
- Custom plug-in: powerful plug-in mechanism supports free expansion.
- Extensible: the easy-to-use plug-in mechanism facilitates the expansion of functions.
- High performance: the performance is excellent among many gateways.
- Version control: support release and multiple rollbacks of operations.
- Management backend: configure the gateway cluster through the management backend interface.
We compare Fizz with Spring's official spring-cloud-gateway, using the same environment and conditions, and the test objects are under single node.
- Intel(R) Xeon(R) CPU X5675 @ 3.07GHz * 4
- Linux version 3.10.0-327.el7.x86_64
- 8G RAM
product name | QPS | 90% Latency(ms) |
---|---|---|
direct access | 9087.46 | 10.76 |
fizz-gateway | 5927.13 | 19.86 |
spring-cloud-gateway | 5044.04 | 22.91 |
-
Fizz-gateway-community: Community Edition
-
Fizz-manager-professional:Management backend professional version (backend)
-
Fizz-admin-professional:Management backend professional version (frontend)
Fizz-gateway-community | Fizz-manager-professional | Fizz-admin-professional |
---|---|---|
v1.0.0 | v1.0.0 | v1.0.0 |
v1.1.0 | v1.1.0 | v1.1.0 |
v1.1.1 | v1.1.1 | v1.1.1 |
v1.2.0 | v1.2.0 | v1.2.0 |
Starting from v1.3.0, the frontend and backend of the management backend are merged into one package
-
Fizz-gateway-community: Community Edition
-
Fizz-manager-professional:Management backend professional version
Fizz-gateway-community | Fizz-manager-professional |
---|---|
v1.3.0 | v1.3.0 |
v1.4.0 | v1.4.0 |
v1.4.1 | v1.4.1 |
v1.5.0 | v1.5.0 |
v1.5.1 | v1.5.1 |
Please download the corresponding management backend version according to the version of the community version
Detailed deployment tutorial>>>
Install the following dependent software:
-Redis 2.8 or above -MySQL 5.7 or above -Apollo Configuration Center (optional) -Nacos or Eureka Service Registry (optional)
Dependent installation can refer to detailed deployment tutorial
Download the fizz-manager-professional installation package from github's releases (https://github.com/wehotel/fizz-gateway-community/releases)
Description:
- The
{version}
that appears in the following installation steps represents the version number of the management backend used, such as1.3.0
.
installation:
- Unzip the
fizz-manager-professional-{version}.zip
installation package - For the first installation, execute the
fizz-manager-professional-{version}-mysql.sql
database script, upgrade from a low version to a high version, and choose to execute the corresponding upgrade script in the update directory - Modify the
application-prod.yml
file, and modify the relevant configuration to the configuration of the deployment environment - Linux startup Execute the
chmod +x boot.sh
command to increase the execution authority ofboot.sh
; execute the./boot.sh start
command to start the service, support start/stop/restart/status commands - Windows startup Execute
.\boot.cmd start
command to start the service, support start/stop/restart/status command - After the service is started, visit http://{deployment machine IP address}:8000/#/login, and log in with the super administrator account
admin
passwordAa123!
Description:
- Support configuration center: apollo, nacos, support registration center: eureka, nacos.refer to application.yml file with more detailed configurations.
- If you use the apollo configuration center, you can move the content of the application.yml file to the configuration center (the application name on apollo is: fizz-gateway); if you don't use apollo, you can remove the apollo parameter in the startup command below.
- The
{version}
that appears in the following installation steps represents the version number of the gateway used, such as1.3.0
.
Installation method 1: start by script:
- Download the latest code of fizz-gateway-community, modify the configuration of the configuration center, registry, and redis in the application.yml configuration file (redis configuration needs to be consistent with the management backend), and use the maven command
mvn clean package -DskipTests=true
Build and put the built fizz-gateway-community-{version}.jar and boot.sh in the same directory - Modify the apollo connection and JVM memory configuration of the boot.sh script
- Execute
./boot.sh start
command to start the service, support start/stop/restart/status command
Installation method 2: start by IDE:
- The latest code on the local clone repository
- Import the project fizz-gateway into the IDE
- After the import is complete, config the project startup configuration and modify the configuration center, registry, and redis in the application.yml configuration file (redis configuration needs to be consistent with the management backend) configuration, and add
-Denv=dev -Dapollo.meta to the VM option =http://localhost:66
(Apollo configuration center address)
Installation method 3: start by jar:
- The latest code on the local clone warehouse, modify the configuration of the configuration center, registry, and redis in the application.yml configuration file (redis configuration needs to be consistent with the management backend)
- Execute the Maven command
mvn clean package -DskipTests=true
package in the project root directory fizz-gateway-community - Enter the target directory and use the command
java -jar -Denv=DEV -Dapollo.meta=http://localhost:66 fizz-gateway-community-{version}.jar
to start the service
Finally visit the gateway, the address format is: http://127.0.0.1:8600/proxy/[Service name]/[API Path]
Fizz官方技术交流①群(已满)
Fizz官方技术交流②群(已满)
Fizz官方技术交流③群:512164278
服务器减少50%,研发效率提高86%,我们的管理型网关Fizz自研之路
简单易用的微服务聚合网关首选:Fizz Gateway安装教程
大厂推荐使用的网关解密:Fizz Gateway管理后台使用教程
架构师效率快的终极原因:Fizz Gateway网关之服务编排
-
The fizz-gateway-community community version of the gateway core project is open in GNU v3 and can be used for free.
-
Management backend projects (fizz-manager-professional) as commercial versions only open binary packages free download, and For commercial projects, please contact us ([email protected]) for authorization.