redb 3.4.0 Adds Replay Checkpoints, Shared Runtime Layer and Declarative Secrets Handling for .NET Ecosystem
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.
Related articles
OpenAI Releases GPT-6.1 Terra: Cost-Effective Model Focused on Computer Control, Image Analysis and Practical Automation
OpenAI has launched GPT-6.1 Terra, a new model positioned between its high-end GPT-6 Astra and more affordable options in the GPT-6 family. The model emphasizes real-world computer interaction, visual understanding of documents and interfaces, and reduced error rates rather than raw reasoning benchmarks. It supports a 1.05 million token context window, image inputs, and tool use through the Responses API while cutting input token prices by half compared with its predecessor. Published benchmarks show substantial gains on Terminal-Bench 4.0, OSWorld 2.1 and Agents' Last Exam, with error rates dropping sharply at both low and maximum reasoning levels. OpenAI stresses that the model still requires human oversight for high-stakes actions and does not directly process audio or video. The release targets developers and enterprises seeking reliable automation of repetitive multi-step tasks at lower cost than flagship models.
Yandex Black October: How Architectural Flaws and Capacity Mismanagement Turned Data Center Losses Into a 11-Day Fintech Coma
In October 2026 three Yandex data centers in Central Russia were physically destroyed within days, triggering the collapse of Yandex Cloud and multiple core services. Between the first and third site failures engineers had 74 hours to restore quorum and rebalance workloads yet failed to do so because Control Plane components remained tied to the lost zone and spare capacity had been eliminated to cut costs. Core banking and BNPL systems entered Read-Only mode after losing quorum, forcing a complete stop-the-world reconciliation that lasted until 22 October. Backups stored inside the same regional S3 buckets proved unusable, resulting in a seven-day RPO and primary-key collisions after restoration. The incident exposed that Metro-Cluster designs had been incorrectly treated as full Disaster Recovery and that aggressive AP microservice patterns created logical split-brain conditions outside the database layer.
Astra Group Releases Low-Code Astra AI Platform for Building Corporate AI Agents in Closed Environments
Astra Group has launched the Astra AI Platform, a low-code constructor designed for creating corporate AI applications that operate entirely within closed circuits without reliance on foreign clouds. The platform targets small and medium businesses as well as large corporations, enabling rapid deployment of AI secretaries, technical support assistants, and other agents in days rather than months. It forms part of the broader Astra AI ecosystem and includes two main constructors: one for machine learning model training and deployment, and another for LLM-based language assistants, document search, and process automation. Users can assemble scenarios from visual blocks, debug them in real time, or extend functionality with custom Python code when needed. The solution supports RAG-based knowledge bases, integration with external tools such as CRM and ERP systems, and the coordination of multiple agents for distributed task handling. One demonstrated use case involves processing ten pages of engineering drawings and specifications in five minutes to prepare data for downstream systems. The product is already listed in the Russian domestic software registry and available to customers.
Multi-Tenancy Isolation in VictoriaMetrics, VictoriaLogs and Grafana: Building Client Separation in a Shared Stack
Voltir runs a single shared monitoring stack consisting of VictoriaMetrics, VictoriaLogs, Grafana and vmalert for all customers instead of deploying separate instances per tenant. Isolation relies on numeric account IDs enforced at every layer: nginx validates tokens against the platform API before proxying writes, Grafana data sources hard-code tenant accounts, and vmalert rules receive automatic account filters. The team discovered that a single malformed rule or template could break alerting for every tenant because vmalert loads the entire rules directory at once. They also found that Grafana automatically created personal organizations granting Org Admin rights, accumulating hundreds of orphaned organizations and users that consumed disk space and resources. A dedicated cleanup module plus hourly reconciliation now removes rules, organizations, series and users when a tenant is deleted, while isolation tests verify both data and API objects across tenants.