Microservices Architecture Explained

GCXONE employs a microservices architecture built on Kubernetes to provide scalable, resilient, and maintainable cloud services. This architecture enables the platform to support hundreds of device manufacturers while maintaining a unified interface and API.

⚙️

Microservices

Scalable & Resilient

Architecture Benefits

🌐

Universal Support

Specialized proxies handle device-specific protocols

📈

Scalability

Each service scales independently based on demand

🛡️

Resilience

Service failures are isolated and don't cascade

🚀

Rapid Development

New device support without affecting core services

---

The Universal Translator: Proxy Architecture

How Proxy Architecture Works

Proxies act as "universal translators" between GCXONE's standardized API and device-specific protocols

Core Concept

🔌 Standardized Interface

• GCXONE Core uses the same API for all proxies
• Consistent input signatures
• Unified output schemas
• Device complexity hidden from core

🔄 Protocol Translation

• Each proxy understands manufacturer protocols
• Translates between protocols and standards
• New devices = new proxy service
• No core system changes needed

Communication Flow

Request Flow Through Microservices

Step 1-3: Request Initiation

1. User Request

User initiates an action through web or mobile interface (e.g., PTZ control, live stream, playback).

2. API Gateway

Request goes to GCXONE API, the single entry point for all client requests.

3. Routing

API identifies the request type and device manufacturer, then consults a dictionary of proxy endpoints.

Example Endpoint Dictionary

{
"Hikvision": "hikproxy.nxgen.cloud",
"Dahua": "dahuaproxy.nxgen.cloud",
"Axis": "axisproxy.nxgen.cloud",
"Hanwha": "hanwhaproxy.nxgen.cloud"
}

Step 4-6: Protocol Translation

4. Proxy Call

API makes an HTTP call to the appropriate proxy with standardized JSON payload.

5. Protocol Translation

Proxy translates the standardized request to device-specific protocol (SDK, REST, TCP, etc.).

6. Device Communication

Proxy communicates with the physical device using the native protocol.

Translation Example

Standardized Request:

{"action": "ptz_move", "direction": "right"}

Hikvision Protocol:

ISAPI/PTZCtrl/channels/1/continuous

Step 7-9: Response Handling

7. Device Response

Device sends acknowledgment or result back to the proxy.

8. Response Translation

Proxy translates device response to standardized format.

9. UI Update

API receives standardized response and updates the user interface.

Benefits

• ✅ Consistent API regardless of device
• ✅ Device-specific logic isolated
• ✅ Easy to add new device support
• ✅ Fault isolation

Device Protocol Support

📡 Supported Protocols

Protocol Type	Usage Examples	Device Examples	Notes
HTTP/REST/Open API	Device info, camera lists, PTZ control	Hikvision, Hik-Connect Pro	Not suitable for streaming
SDK	Live stream, playback, video files, two-way audio	Hikvision (.NET HcNetSDK)	Provides TCP layer for streaming
TCP/Native TCP	Legacy devices, alarm transmission	ADPRO	Event push via TCP
Webhooks/HTTP	Event transmission from IP cameras	Axis, Hanwha	HTTP requests to camera rules
WebSocket Subscription	Real-time event streaming	Axxon	Pulled by GCXONE via websocket
SIA DC-09	Alarm transmission	Reconeyez	Routed through Talos receiver

Infrastructure & Scaling

☁️ Kubernetes Orchestration

• Private EKS Clusters: 75% of logic on secure nodes
• Containerized Services: All services in Docker containers
• Service Mesh: Kubernetes networking
• Load Balancing: Automatic load distribution
• High Availability: Automatic failover

📈 Auto-Scaling (HPA)

• Horizontal Scaling: Add pods, not vertical scaling
• 75% CPU Threshold: Triggers new pod creation
• 2-3 Minute Lead Time: Ensures pods ready before 100%
• Service-Specific: Each service scales independently
• Resource Efficiency: Scale only what's needed

Services Requiring Autoscaling

🧠

CVIDR

AI engine for event detection and image processing

📹

Streaming

Video streaming and transcoding services

⚙️

Proxies

Device proxy services (e.g., Adpro proxy)

🔔

Events

Alarm and event processing services

Microservices Components

🌐 Core Services

• API Gateway: Single entry point
• Authentication: Auth0 integration
• Device Management: Registration & monitoring
• User Management: Accounts & permissions

⚙️ Proxy Services

• Hikvision Proxy: SDK & ISAPI
• Dahua Proxy: DoLynk & native
• Axis Proxy: HTTP/Webhook
• Other Proxies: Manufacturer-specific

🔧 Supporting Services

• Streaming: Video & WebRTC
• AI/ML (CVIDR): Event detection
• Messaging: MQTT routing
• Storage: Video & snapshots

Architecture Benefits

✅ Advantages

• Scalability: Independent scaling per service
• Resilience: Fault isolation prevents cascading failures
• Maintainability: Isolated device-specific logic
• Development Speed: Rapid feature addition
• Technology Diversity: Different tech stacks per service

🎯 Best Practices

• Single Responsibility: One clear purpose per service
• API-First Design: Well-defined service APIs
• Stateless Services: No session state
• Circuit Breakers: Prevent cascading failures
• Monitoring: Service-specific metrics

Related Articles

• Proxy Architecture & Communication Flow
• Cloud Architecture Overview
• Multi-Tenant Architecture
• Hierarchy Model

---

Need Help?

If you have questions about the microservices architecture or need technical assistance, check our Troubleshooting Guide or contact support.