Gateway

PoCAT Gateway_

Netty-backed HTTP connectors plus XML-declared routes, Servit-hosted handlers, filters, outbound channels, and EIP-friendly wiring—matching the OSS gateway tarball layout—not a solitary reverse proxy tier.

Architecture

Operational layout

ServiceContainers encapsulate transports: connectors ingest traffic, routers and processors evaluate patterns, Servits serve deliveries, and outbound adaptors integrate HTTP, MQTT, or broker channels.

Message Converter Layer
Transforms and standardizes various message formats between heterogeneous systems.
  • Configurable templates & serializers
  • Custom filters + upstream HTTP clients
  • Enterprise file drops via outbound channels
  • Composable Servits for bespoke protocols
Router Layer
Intelligent routing engine for directing messages to appropriate backend services.
  • Declarative matchers from route XML
  • Configurable upstream endpoints
  • Operational logging per worker pool
  • Channel-level retries delegated to EIP patterns
Filter Layer
Advanced filtering system for security, validation, and request optimization.
  • Authentication & authorization
  • Rate limiting & throttling
  • Request validation
  • Monitoring & analytics

Gateway Flow Architecture

Client Request
Filter Layer
Message Converter
Router
Backend Service
Configuration

Gateway Configuration

Publish XML under config/, context/, routes/ folders—matching the tarball layout delivered with Gateway releases.

Basic Gateway Configuration

Start with a minimal configuration to get your gateway up and running quickly.

Server Configuration
Configure port, host, and basic server settings
Environment Provider
Set up connection to your environment resources
Logging Configuration
Configure logging levels and output formats
# config/gateway-config.xml (excerpt)
<gateway>
<name>production</name>
<worker-pool-size>32</worker-pool-size>
<response-channel>default-response</response-channel>
<services>... list HTTP/MQTT services ...</services>
</gateway>
# Shared endpoints, brokers, JDBC pools, ...
context/context.xml
# Per-route descriptors under routes/<group>/*
Performance

Gateway Performance

Built on Netty framework with asynchronous processing for maximum throughput and minimal latency.

Measure*
Profile on your JVM + HW
High throughput*
Throughput depends on workloads*
SLA*
Depends on infra
Manual ops
Scaling

Technical Specifications

Runtime Environment

  • • Java 11+ or Java 17 LTS
  • • Netty 4.1+ framework
  • • Minimum 2GB RAM
  • • 4+ CPU cores recommended
  • • Linux/Windows/macOS support

Supported Protocols

  • • HTTP/1.1 and HTTP/2
  • • WebSocket connections
  • • gRPC protocol support
  • • TCP/UDP proxying
  • • TLS 1.2/1.3 encryption

Integration Features

  • • Kubernetes native
  • • Docker containerized
  • • Prometheus metrics
  • • OpenTracing support
  • • Hot configuration reload
Enterprise Benefits

Unlock Enterprise Value with Pocat Gateway

Empower your organization with a next-generation Gateway designed for enterprise-grade performance, security, and scalability.

Unified Integration
Seamlessly connect heterogeneous systems and data sources across your enterprise.
Streaming Pipelines
Real-time data ingestion and processing for mission-critical applications.
High Performance
Sub-millisecond latency and massive throughput for demanding workloads.
Legacy Support
Seamlessly integrate legacy systems with modern APIs and protocols.
Modular Design
Customize and extend the gateway with a flexible plugin architecture.
AI Transformation
Unlock the power of AI with intelligent routing and data enrichment capabilities.
Quick Start

Deploy Your Gateway

Get your Pocat Gateway running in minutes with our simple deployment options.

Docker Deployment

# Pull and run Pocat Gateway
docker pull pocat/gateway:latest
docker run -d \
--name pocat-gateway \
-p 8080:8080 \
-v ./config:/etc/pocat \
pocat/gateway:latest
# Gateway available at http://localhost:8080
Production-ready container image
Automatic health checks included
Volume mounting for configuration

Kubernetes Deployment

# Deploy with Helm chart
helm repo add pocat https://charts.pocat.dev
helm install gateway pocat/gateway \
--set replicas=3 \
--set service.type=LoadBalancer
# Tune worker pool & access logging via XML knobs
kubectl apply -f gateway-deployment.yaml
Helm chart with best practices
Horizontal Pod Autoscaling
Service mesh integration ready