How to Make Spring Cloud Gateway Production‑Ready with EDAS Enhancements

Background

Spring Cloud Gateway is a popular gateway component in the Spring Cloud ecosystem, but the open‑source version has known issues such as memory leaks caused by Netty’s buffer allocation and a lack of route‑definition validation.

EDAS Enhancements

EDAS applies years of CSB experience to address these problems. It adds a startup parameter -Dio.netty.allocator.type=unpooled to avoid off‑heap memory leaks, and sets spring.cloud.gateway.fail-on-route-definition-error=false to prevent the gateway from failing when a route definition contains a typo.

Key Features

Dynamic configuration via a white‑screen console.

Custom plugin development.

Route debugging and testing.

Rate‑limiting and degradation.

Enhanced observability, including access logs.

Quick Start

Package an existing Spring Cloud Gateway application as a JAR or container image and deploy it on EDAS, or use the provided demo package which already connects to a Nacos registry. After deployment, EDAS adds a “Gateway” menu where routes can be created.

Example curl test:

~ curl 121.xx.xx.xx/httpbin/get
{
  "args": {},
  "headers": { ... },
  "origin": "121.xx.xx.xx, 47.xx.xx.xx",
  "url": "http://121.xx.xx.xx/get"
}

Route Configuration

Routes can be defined in YAML following the standard Spring Cloud Gateway schema. Two examples are provided:

spring:
  cloud:
    gateway:
      routes:
        - id: r-demo
          predicates:
            - Host=demo.com
          filters:
            - AddRequestHeader=a,b
          uri: http://demo.com
          order: 1000
        - id: r-demo-2
          predicates:
            - Path=/demo-2/**
          filters:
            - StripPrefix=1
          uri: lb://service-provider
          metadata:
            ccc: ddd
            eee: 10
          order: 1000

Observability

EDAS adds an access log at /home/admin/.opt/ArmsAgent/logs/scg-access.log. Each entry records fields such as dateTime, traceId, clientIp, method, path, requestSize, backendStatusCode, status, and responseSize.

Future Roadmap

More plugins (authentication, rate limiting, CORS).

Cross‑microservice‑space access.

Metrics for gateway and business monitoring.

Single‑machine QoS troubleshooting.