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
Bypassing Paid Export on AI 3D Generation Sites via Browser Network Inspection
A detailed walkthrough shows how users can retrieve AI-generated 3D models in GLB format from services that normally require a paid subscription for export. The method relies on opening the browser developer console, filtering network requests for .glb files after model generation completes, and opening the intercepted asset in a new tab. Examples using Tripo3D and Hi3D demonstrate that the generated model and textures are already present on the client side even when the export button remains disabled. Additional steps address compatibility issues with 3ds Max by recommending conversion through gltf.report with Draco compression before import. The technique also covers post-processing in ZBrush for auto-retopology and format conversion to OBJ. The article notes that such workarounds exist because many AI platforms limit free exports while still rendering full models locally.
National Platform Max Begins Testing Advertising Tools to Monetize User Attention
The Russian national platform Max has started internal testing of new advertising instruments designed to convert user attention into sellable ad inventory. According to the company's press service, the tests are already underway inside the application, although the exact placement, visual format, and eligibility criteria for advertisers remain undisclosed. The move marks a significant shift for the platform, which previously operated without visible commercial advertising. Observers note that Max could become one of the largest domestic digital advertising channels if the tests prove successful. No timeline has been given for a public rollout or for the publication of detailed advertising policies.
Yandex Drops Earbuds Under X-Ray Microtomography: Detailed Internal Analysis of First AI-Powered TWS Headphones
Engineers used non-destructive X-ray microtomography to examine Yandex Drops, the company's first TWS earbuds featuring the Alice AI voice assistant. The scan revealed an eight-layer HDI PCB, three microphones per earbud arranged in a dual feedforward plus feedback ANC configuration, an 11 mm driver, and a QFN-packaged SoC with NPU. No hardware disconnect point was identified in the microphone signal path within visually accessible traces, connectors, and vias. Battery dimensions, coil windings in the case, and internal flex routing were measured directly from calibrated voxel data. The study also confirmed contact-based charging via spring-loaded claw contacts and a Hall-effect sensor in the case lid. The work demonstrates how industrial micro-CT can support hardware security reviews without destroying the sample.
Russia Sets Tech Collection Fees: Smartphones from 250 Rubles, Laptops from 500 Rubles Starting December 2026
The Russian Ministry of Industry and Trade has proposed specific rates for a new technological collection fee that will apply to imported smartphones, laptops, and landline telephones. Payments begin on December 1, 2026, with the final amount depending on whether the device model is registered in the national marking system. Base rates are reduced by 33 percent for registered models and increased by the same margin for unregistered ones. The fees were calculated using 2025 median customs values and a 4 percent inflation target. Manufacturers and importers must pay the collection, though costs are expected to reach consumers through higher retail prices. Separate lower rates apply to corded phones with wireless handsets and basic mobile phones.