Brokers and Rules System

Overview

The Ripple framework utilizes a sophisticated broker system combined with JQ-based rules to manage communication between Firebolt applications and various backend services. This architecture provides flexible routing, transformation, and protocol handling capabilities.

Core Components

1. Endpoint Broker

The Endpoint Broker serves as the primary routing mechanism in Ripple, directing requests to appropriate backend services based on configured rules. It supports multiple endpoint types including Thunder, HTTP, WebSocket, and custom extensions.

Learn more about Endpoint Broker

2. Thunder Broker

The Thunder Broker specifically manages communication with Thunder plugins through WebSocket connections. It handles connection management, request routing, and subscription management for Thunder-based services.

Learn more about Thunder Broker

3. Rules Configuration

The rules system, primarily defined in ripple.common.rules.json, provides a declarative way to configure request routing, transformations, and response handling. It uses JQ expressions for powerful data transformation capabilities.

Learn more about Ripple Common Rules

Learn more about JQ Rule Functions