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.
- Finlight Data Listener (FDL)
WebSocket client connecting to Finlight, subscribing to real-time financial news feeds and publishing enriched articles to RabbitMQ queues.
- Finlight Data Processor (FDP)
RabbitMQ consumer processing enriched news articles from the FDL queue, running FinlightDataAnalyzer to cache articles in Redis and publish updates to downstream consumers.
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 |
FDL |
fdl.Dockerfile / fdl_otel.Dockerfile |
kuhl_haus.servers.fdl_server:app |
FDP |
fdp.Dockerfile / fdp_otel.Dockerfile |
kuhl_haus.servers.fdp_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:
Metadata
Release files for kuhl-haus-mdp-servers 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| kuhl_haus_mdp_servers-0.3.0.tar.gz | 19.4 kB | With provenance | Details for kuhl_haus_mdp_servers-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| kuhl_haus_mdp_servers-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for kuhl_haus_mdp_servers-0.3.0-py3-none-any.whl |
Total release size: 39.3 kB
Release files / kuhl_haus_mdp_servers-0.3.0.tar.gz
| Download URL | kuhl_haus_mdp_servers-0.3.0.tar.gz |
|---|---|
| Size | 19.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
21064ec9fd40ca6d5b5ec2b37cda2735acce78c02a0c3fd3acf16f5be4c07f22
|
|
BLAKE2b-256 checksum How to use checksums |
d3e7980aaf0d863853ed865781d1288e2e0595df1a83d612f52360f399d85d05
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 8, 2026.
Transparency logRelease files / kuhl_haus_mdp_servers-0.3.0-py3-none-any.whl
| Download URL | kuhl_haus_mdp_servers-0.3.0-py3-none-any.whl |
|---|---|
| Size | 19.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
49e36be47e0d48092e20b9f9fa43965a09c79c7bbc3f618970cd32c6484acbdb
|
|
BLAKE2b-256 checksum How to use checksums |
f1bea06325f8c77e6e7c503129a0447029f80dfe5c3fa8bd4c8e29a771b8dc05
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 8, 2026.
Transparency logSecurity for kuhl-haus-mdp-servers 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for kuhl_haus_mdp_servers-0.3.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 8, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.