SIA‑Gateway: A Distributed Microservice Gateway System – Architecture, Features, and High Availability

1. Background

Software architecture has continuously evolved from early C/S models (PB, Delphi) to browser‑based B/S architectures, then to Java‑centric J2EE and SOA approaches, and finally to microservice architectures that emphasize loose coupling and high cohesion.

Monolithic systems caused data silos and required ETL tools; as enterprise applications grew, real‑time interaction and integration via XML, web services, and ESB became necessary, leading to the adoption of HTTP/REST and JSON as best practices.

2. Microservice Architecture Characteristics

Heterogeneity : Different services can use the most suitable technology stack, allowing low‑risk experimentation on a single service.

Isolation : Independent services simplify fault localization and form the basis for scalability.

Scalability : Individual services can be horizontally scaled based on performance needs, unlike monoliths that require whole‑system scaling.

Simple Deployment : Each service can be deployed independently, enabling faster releases, quick rollbacks, and agile delivery.

Flexibility : Open APIs allow external consumption and composition of services, turning a monolith into reusable, combinable microservices.

3. Microservice and Gateway Technology

A microservice gateway protects, enhances, and controls access to microservices, handling authentication, authorization, traffic limiting, and providing a unified entry point.

Gateways are typically classified into traffic gateways and business gateways, each focusing on different concerns.

4. SIA‑Gateway

SIA‑Gateway is a SpringCloud‑based distributed microservice gateway offering simplicity, visual management, high scalability, multi‑tenant support, and comprehensive service governance.

Key Features :

Easy Docker‑based deployment and delivery.

Compatibility with SpringBoot microservices and traditional HTTP‑URL load balancing.

Java‑based plugin extensibility with dynamic loading.

Multi‑tenant and role‑based gateway management.

Real‑time topology visualization and cluster monitoring.

Service governance including dashboards, logs, circuit‑breaker, and alerting.

Support for multiple registration centers and dynamic routing components.

The architecture consists of CORE nodes handling HTTP requests and an Admin cluster (Admin, Service, Stream, Monitor) for management.

High‑availability is achieved through clustering (minimum two nodes), health‑check endpoints (Kubernetes liveness probes or cron‑based checks), and a backup gateway (API‑GATEWAY‑CORE) that synchronizes routing information and can take over traffic via Nginx failover.

The system follows the Unix philosophy of providing mechanisms rather than policies, exposing interfaces for third‑party Java filters that can be packaged, uploaded, stored, distributed, and dynamically loaded at runtime.

Visualization components include global cluster dashboards, real‑time routing topology, gateway cluster management UI, component management UI, log aggregation via EKK, circuit‑breaker monitoring, and fine‑grained URL statistics.

5. Summary

Microservice architecture reduces system complexity through layering and decoupling, but successful adoption depends on organizational culture, team capability, and proper technology selection.

SIA‑Gateway aligns with business system technology stacks, offers mature ecosystem compatibility, and provides the necessary infrastructure to ensure high availability, scalability, and observability for microservice‑based applications.

Future challenges such as distributed transactions, network latency, and fault tolerance require continued investment in robust microservice governance and infrastructure.