kuhl-haus-mdp-servers 0.2.0

Container image build repository for market data processing servers

kuhl-haus-mdp-servers

Container image build repository for market data platform data plane servers.

Overview

This package provides the server entry points and Docker container images for the Kuhl Haus Market Data Platform (MDP) data plane. Each server wraps components from the kuhl-haus-mdp library and runs as an independently scalable container in Kubernetes.

Servers

Market Data Listener (MDL)

WebSocket client connecting to Massive.com, routing events to RabbitMQ queues with minimal processing overhead.

Market Data Processor (MDP)

Horizontally-scalable event processor with semaphore-based concurrency, delegating to pluggable analyzers and writing results to Redis cache.

Leaderboard Analyzer (LBA)

Redis pub/sub consumer running leaderboard and trade analyzers with sequential message processing.

Widget Data Service (WDS)

FastAPI/WebSocket-to-Redis bridge providing real-time streaming to client applications with fan-out pattern.

Each server has a standard Dockerfile and an OpenTelemetry-instrumented variant (*_otel.Dockerfile) for production observability.

Container Images

Server	Dockerfile	Entry Point
MDL	mdl.Dockerfile / mdl_otel.Dockerfile	kuhl_haus.servers.mdl_server:app
MDP	mdp.Dockerfile / mdp_otel.Dockerfile	kuhl_haus.servers.mdp_server:app
LBA	lba.Dockerfile / lba_otel.Dockerfile	kuhl_haus.servers.lba_server:app
WDS	wds.Dockerfile / wds_otel.Dockerfile	kuhl_haus.servers.wds_server:app

All images extend base.Dockerfile, which installs dependencies and the package in editable mode.

Code Organization

The platform consists of four main packages:

• Market data processing library (kuhl-haus-mdp) - Core library with shared data processing logic

• Backend Services (kuhl-haus-mdp-servers) - Market data listener, processor, and widget service

• Frontend Application (kuhl-haus-mdp-app) - Web-based user interface and API

• Deployment Automation (kuhl-haus-mdp-deployment) - Docker Compose, Ansible playbooks and Kubernetes manifests for environment provisioning

Configuration

All servers are configured via environment variables. See the Configuration Reference for the full list of variables per server, including defaults and descriptions.

Documentation

For architecture details, component descriptions, and API reference, see the kuhl-haus-mdp documentation on Read the Docs.

Additional Resources

📖 Blog Series:

• Part 1: Why I Built It

• Part 2: How to Run It

• Part 3: How to Deploy It

• Part 4: Evolution from Prototype to Production

• Part 5: Wave 1 Complete: Bugs, Bottlenecks, and Breaking 1,000 msg/s