jhipster-gateway

JHipster Gateway

Configure and manage the JHipster Gateway as the single entry point for microservices, handling routing, rate limiting, CORS, and serving the Angular frontend.

When to Use

• When configuring routes to backend microservices
• When setting up rate limiting on API endpoints
• When configuring CORS for cross-origin requests
• When checking health/status of backend services
• When debugging routing issues

Available Operations

1. Configure service routes with load balancing
2. Add rate limiting per route
3. Configure CORS policies
4. Monitor service health via actuator
5. Add custom gateway filters

Multi-Step Workflow

Step 1: Configure Routes

# application.yml
spring:
  cloud:
    gateway:
      routes:
        - id: demand-service
          uri: lb://demand-service
          predicates:
            - Path=/api/demands/**,/api/tasks/**
        - id: agent-service
          uri: lb://agent-service
          predicates:
            - Path=/api/agents/**,/api/teams/**
        - id: tracking-service
          uri: lb://tracking-service
          predicates:
            - Path=/api/tracking/**,/api/events/**
      default-filters:
        - TokenRelay

Step 2: Add Rate Limiting

spring:
  cloud:
    gateway:
      routes:
        - id: demand-service
          uri: lb://demand-service
          predicates:
            - Path=/api/demands/**
          filters:
            - name: RequestRateLimiter
              args:
                redis-rate-limiter.replenishRate: 10
                redis-rate-limiter.burstCapacity: 20
                key-resolver: "#{@userKeyResolver}"

@Bean
public KeyResolver userKeyResolver() {
    return exchange -> Mono.just(
        exchange.getRequest().getHeaders().getFirst("Authorization") != null
            ? exchange.getRequest().getHeaders().getFirst("Authorization")
            : exchange.getRequest().getRemoteAddress().getAddress().getHostAddress()
    );
}

Step 3: Configure CORS