Smart Wave is an advanced telemetry and environmental monitoring platform used in maritime operations. It aggregates real-time data from buoys, vessels, and ocean sensors for processing, analytics, and compliance reporting.

Deploying Smart Wave requires a reliable and secure application delivery infrastructure to ensure uninterrupted data flow from remote maritime sensors to backend systems. This is where RELIANOID excels — providing smart load balancing, failover, and end-to-end observability.

Understanding the Smart Wave Architecture #

Smart Wave is typically deployed as a multi-tier application:

• IoT Edge Ingestion: Devices sending telemetry (MQTT, HTTP POST, TCP)
• Core Services: APIs for data handling, normalization, and analytics
• Dashboard: Web UI for marine operators and research centers
• Data Lake / Time-Series DB: InfluxDB, PostgreSQL, or custom storage

RELIANOID-Based Topology for Smart Wave #

Smart Wave needs a hybrid load balancing model:

• L7 HTTP/HTTPS: For dashboard and REST APIs
• L4 TCP: For MQTT brokers, sensor ingestion, and DB access
• SSL Offloading: For performance and centralized TLS management
• High Availability: For active-passive failover between shore and satellite relays

    [Ocean Sensors]             [Fleet Terminals]
         │                            │
   ┌─────▼─────┐              ┌───────▼───────┐
   │ MQTT / TCP│              │  REST / HTTPS │
   └─────┬─────┘              └───────┬───────┘
         │                            │
     ┌───▼────────────────────────────▼───┐
     │         RELIANOID ADC Gateway      │
     └───┬────────────────────────────┬───┘
         │                            │
  ┌──────▼───────┐            ┌───────▼───────┐
  │ Smart Wave UI│            │ Ingestion APIs│
  └──────────────┘            └───────────────┘

Configuration #

Different virtual services for both Smartwave Dashboard and broker:

HTTP Load Balancing for the Dashboard #

Here it is the service session persistence for Smartwave Dashboard HTTPs service:

Then, set the health check and backends with the real Smartwave servers:

MQTT Broker (TCP L4) #

Here it is the service settings for scheduler and session persistence for the Smartwave broker service:

Then, set the backends:

API Layer Routing Based on Path #

Create new virtual service for Smartwave API:

Create the API admin service using the path /api/admin without session persistence and https health check:

Create the API data service using the path /api/data without session persistence and https health check:

Observability with RELIANOID #

Smart Wave platforms generate massive telemetry data — RELIANOID supports:

• Metrics export for system and traffic statistics
• Centralized logging for debugging ingestion issues
• Graphs with per-node, per-protocol views
• Custom health checks for MQTT, HTTP APIs, and external dependencies

Security Features #

• Mutual TLS (mTLS): Between buoys/devices and API endpoints
• Web Application Firewall: Protection for dashboard & admin APIs
• DoS/DDoS Mitigation: Rate limiting and connection caps per source IP
• JWT/Token Header Inspection: Drop requests lacking auth headers

Additional Benefits with RELIANOID #

• Handles satellite communication edge cases (latency, retry handling)
• Supports hot configuration reloads for live changes
• Allows geo-based routing (shore stations, data centers)
• Supports connection mirroring for test/staging without affecting production

Example Smart Wave Use Case #

A marine institute runs Smart Wave nodes on offshore platforms collecting wave height, water quality, and GPS data. RELIANOID ensures the data reaches the main cluster (via TCP and HTTPS) with no interruption, load is balanced between ingestion microservices, and anomalies are blocked at the edge.

RELIANOID is ideal for powering Smart Wave’s real-time data flow — across harsh ocean conditions, constrained networks, and latency-prone links. With advanced load balancing, zero-downtime updates, and tight security controls, RELIANOID guarantees operational continuity for maritime telemetry systems.