I built an Apache Camel-style integration framework for .NET — 22 transports, 30+ EIP patterns, Apache 2.0
After a year of building, I just open-sourced an integration ecosystem for .NET. Three repos, all Apache 2.0:
- redb.Route — Camel-style fluent C# DSL with 22 transports (Kafka, RabbitMQ, Redis, SQL polling, HTTP, gRPC, SFTP, MQTT, S3, IBM MQ, AMQP 1.0, Azure SB, Elasticsearch, LDAP, Mail, TCP, WebSocket, SignalR, FTP, Quartz, File). 30+ EIP processors (Splitter, Aggregator, CBR, Recipient List, Dynamic Router, Wiretap, Dead Letter Channel). OpenTelemetry. Compiled expression engine. → https://github.com/redbase-app/redb-route
- redb.Tsak — runtime container. Drop a .dll, hot-reload, cluster (leader election + auto-rebalance), REST API + CLI + Blazor dashboard. Closest analogue is Apache Karaf / Camel K — both JVM-only. → https://github.com/redbase-app/redb-tsak
- redb.Core — typed EAV storage over Postgres/MSSQL with full LINQ. Schema is a C# class with
[RedbScheme]. Values live in typed columns with FK constraints, not JSON blobs. → - https://redbase.app/
- https://github.com/redbase-app/redb
Why?
If you need Apache Camel in .NET — you don't have it. MassTransit / Wolverine / NServiceBus are message buses with 4–7 transports and Saga. Camel itself has 300+ components and 80+ EIP patterns, but it's JVM. There's no .NET project that gives you the full EIP catalogue as first-class DSL with 20+ transports. So I wrote one.
Production state
Running at a 30-year-old national HoReCa food distributor in Russia: 3-node cluster (4 cores / 8 GB / 50 GB SSD per node), ~550 daily users, ~150k orders/month routed through it, ~3 months stable, 10–15% CPU under full load. 43 NuGet packages, ~8.4k downloads.
What I want from this post
Honest criticism. Specifically: Is "another integration framework" the wrong framing for .NET, or is the gap real? redb.Core uses EAV — does the typed-columns + FK design defuse the usual EAV objections, or is the term itself a non-starter? There's a Pro tier (compiled queries, parallel materialization, change tracking). Free tier (everything above) stays Apache 2.0 forever. What would make the split feel fair rather than bait-and-switch? Solo author. Bus factor of 1. Posting to find contributors and harsh feedback. GitHub org: https://github.com/redbase-app Architecture writeup: https://redbase.app/architecture
---
If you have questions or want to discuss use cases —
GitHub Discussions are open: https://github.com/redbase-app/redb-route/discussions