redb 3.4.0 Adds Replay Checkpoints, Shared Runtime Layer and Declarative Secrets Handling for .NET Ecosystem

redb 3.4.0 delivers operational improvements for the .NET integration platform that includes typed storage over Postgres, MSSQL and SQLite, the redb.Route engine modeled after Apache Camel, the Tsak runtime with dashboard and clustering, and redb.Identity for OIDC and OAuth 2.1. The release focuses on post-deployment resilience with replay checkpoints that capture message state at named points inside routes, allowing safe re-execution of downstream steps without duplicating side effects. A shared runtime layer moves framework assemblies into a separate Libs/shared directory so that individual DLLs can be replaced without rebuilding or redeploying the entire Tsak or Identity packages. Secrets are now declared with a [Sensitive] attribute on endpoint options, ensuring URIs containing passwords or keys are sanitized before they reach logs, metrics or health checks. Additional controls include role-based access to management APIs, persistent audit trails and cryptographic signing of dynamically loaded modules. All Pro features remain free on the entire 3.x line with no licensing server required.

HabrJuly 28, 2026Translated from Russian

Read at source

redb 3.4.0 introduces four major capabilities aimed at the day-after-deployment phase of running integration routes on .NET. The ecosystem comprises typed storage redb on top of Postgres, MSSQL and SQLite, the integration engine redb.Route that provides more than thirty connectors modeled on Apache Camel, the redb.Tsak runtime with dashboard, hot-reload and clustering, and redb.Identity implementing OIDC and OAuth 2.1.

The first feature, replay checkpoints, lets developers mark safe points inside a route using the Replayable DSL method. When a downstream step fails, the exchange snapshot captured at the last checkpoint can be replayed without re-executing earlier side effects such as card charges. The mechanism relies on a new IExchange.Snapshot primitive that performs a deep isolated copy, avoiding the shared-body behavior of the existing Clone method used by splitters.

Failed exchanges that carried a checkpoint are automatically placed into a dead-letter queue table. Operators can list, replay or discard these exchanges through the dashboard, REST API or CLI commands. Retention is handled by a standard cron route rather than an internal timer.

The second major change separates the framework assemblies into a Libs/shared directory. Early bootstrap code installs a custom assembly resolver so that redb.Core, providers and connectors are loaded from the shared location. Replacing a single DLL now patches the running system without rebuilding Tsak archives or container images. Version checks ensure that only patch-level differences between the shared layer and the host are permitted.

Secret handling has been moved from heuristic lists to declarative attributes. Endpoint option properties marked with [Sensitive] are automatically redacted by EndpointUri.Sanitize before any logging, OpenTelemetry tagging or health-check output occurs. All thirty-seven credential-bearing options across twenty-two connectors have been annotated.

Finally, the runtime now enforces role-based access on management APIs, records persistent audit events and verifies cryptographic signatures on modules loaded at runtime. redb.Identity has adopted the common ecosystem version number so that compatibility questions are answered by a single version digit.

OpenTelemetry Postgres MSSQL SQLite Apache Camel Kafka MassTransit

ShareX Facebook LinkedIn Reddit

Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in Other

Other

Mail.ru Reduces Lifetime 1TB Cloud Storage Promo to Standard 8GB Quota for Select Users

Mail.ru has begun notifying a small group of long-term Cloud Mail users that their complimentary 1TB storage, originally granted through a 2013-2014 app installation promotion, will be reduced to the standard 8GB free tier. Affected users receive personalized deadlines, with some facing storage limits starting 30 October and final deletion of excess files scheduled for 30 January 2027. The company confirmed the change impacts fewer than 0.5 percent of Cloud Mail users and stated that core free features remain available. Once the 8GB limit is exceeded, uploads, edits, and sharing are blocked while users have three months to download data or purchase additional space before files move to the trash for 14 days prior to permanent removal. This follows a similar reduction of lifetime 100GB storage performed by the service in 2024.

AntiMalwareOct 29, 2026Translated from Russian

Other

Kimi K3 Open Model Surpasses Closed AI Leaders with Million-Token Context and 896 Experts

Kimi K3 is an open-weights model that outperforms closed systems from GPT and Anthropic on several independent benchmarks. Developers achieved this by scaling three dimensions simultaneously: one million tokens of context, deeper layers, and 896 Mixture-of-Experts specialists. The team replaced the standard KV-cache with a fixed-size state matrix updated via the delta-rule, solving numerical instability by clamping the forgetting coefficient alpha between e^-5 and 1. Sequential state updates were parallelized across chips, GPUs, and multi-GPU nodes using the open-source FlashKDA kernel built on CUTLASS. Inter-layer information flow was preserved through learned pseudo-queries that selectively retrieve relevant outputs from prior blocks rather than passing full activations. Load balancing across 896 routed experts uses per-expert quantile thresholds and a distributed histogram method to guarantee fair token allocation without full sorting.

HabrOct 29, 2026Translated from Russian

Other

Innostage Completes Functional Testing of PT NGFW 1.10.3 Across 156 Criteria

Innostage has published the second part of its evaluation of PT NGFW version 1.10.3, focusing on functional capabilities rather than raw performance. The testing covered 156 individual checks grouped into categories such as basic technical features, firewalling, IDS/IPS, web filtering, malware protection, logging, routing, deployment, cryptographic controls and access management. Out of the total, 136 checks passed fully, seven passed with remarks, and 13 did not meet the predefined criteria. Key confirmed functions include high-availability clustering, centralized management via PT-MNGT, AD-based rule application, Site-to-Site VPN, TLS inspection, and Syslog integration with external security systems. Several advanced scenarios, including custom block pages, application risk classification, and centralized software distribution, were not confirmed under the test conditions. The report provides detailed protocol notes that help organizations map product capabilities against their specific infrastructure and regulatory requirements.

HabrOct 29, 2026Translated from Russian