redb 3.4.0 Ecosystem: Enhancing .NET System Operations and FinTech Platform Development
PROSTO24 reports on the release of redb 3.4.0, a significant update to the redb ecosystem designed to enhance the operational aspects of .NET systems. While previous releases focused on system construction, this version is entirely dedicated to addressing post-deployment challenges, including incident recovery, access management, and hot-patching capabilities.
The redb ecosystem comprises a comprehensive suite of tools:
- redb: A typed data storage solution compatible with PostgreSQL, MSSQL, and SQLite.
- redb.Route: An integration engine featuring over 30 connectors, serving as a .NET alternative to Apache Camel.
- redb.Tsak: A runtime environment equipped with a dashboard, hot-reload functionality, and clustering capabilities.
- redb.Identity: An identity server providing OIDC/OAuth 2.1 support.
All components are actively utilized in production environments and are distributed as packages, images, and standalone archives. Version 3.4.0 introduces four key features aimed at improving system stability and manageability in operational contexts.
Streamlining FinTech Platform Development
FinTech platform development often involves creating a substantial amount of code unrelated to core business logic. This foundational layer, encompassing transport mechanisms, retries, dashboards, deployment processes, and monitoring, can account for up to 80% of the total codebase. The redb ecosystem aims to minimize these overheads by providing ready-made solutions for infrastructural tasks.
Four years of redb development have culminated in a robust platform that eliminates the need to build these components from scratch. Notably, all Pro features of the ecosystem are available free of charge across the entire 3.x line, requiring no license keys or servers.
Reference Architecture for Payment Platforms
For developers seeking to build efficient payment systems, a reference architecture is now available. This model provides detailed insights into accounting models, transaction boundaries, module decomposition, cluster topology, integration routes, and recovery points. It demonstrates the practical application of redb components, including the redb typed storage, redb.Route integration engine, redb.Tsak runtime, and redb.Identity server. This architecture serves as a valuable guide, allowing for adaptation to the specific requirements of individual payment systems.
I’ve been using redb for a while now, mainly the redb.Route for integrating with some legacy systems, and it’s been a lifesaver. The 30+ connectors really simplify things, much more straightforward than trying to roll my own. I’ve found the documentation for complex routing scenarios could be a bit clearer, but the community forums are pretty responsive. My tip: don’t underestimate redb.Tsak’s hot-reload; it saves so much time during development and testing. It’s a solid toolkit for .NET, especially for operational concerns.