Kafka

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.

Security Vision 5 Strengthens Connectors, Analytics and Data Handling Features

Security Vision has released an update to its SV5 platform focused on improved integrations, deeper analytics and more flexible configuration management. The release introduces namespace configuration for the WMI connector to execute WQL queries at specified addresses, along with event compression during transmission in connector configurations. An updated librdkafka library now enables the Kafka connector to support SASL/SCRAM authentication for Kafka versions 4.0.0 and higher. Data transformation capabilities have been expanded to allow conversion of numbers between binary, octal and hexadecimal numeral systems, while the Formula transformation adds abs() and sqrt() functions. Linear and bar charts receive new scaling settings, and report generation through the portal has been moved to asynchronous mode to prevent interface freezing during long exports. Additional changes affect object cards, type and directory editors, module settings, graph icon management with mapping conditions converted to filters, and a dedicated section for correlation rules with a general view and editor. The audit log now records grouping changes separately for system and user directories, and the platform blocks execution of disabled connectors through workflows.

Mapping Logical Air Gap Techniques for Secure Network Segmentation

A detailed technical overview explores how organizations can achieve logical air gaps to isolate high-value network segments without completely severing data exchange. The article contrasts classic physical air gaps with everyday reverse proxies and introduces six distinct levels of isolation ranging from physical media to semantic validation. It evaluates each approach across three axes: whether a direct network path remains, which side initiates connections, and whether synchronous responses are possible. Practical constructions such as dual-homed hosts, message brokers, and schema-enforced proxies are examined alongside common misconceptions including reverse tunnels and port knocking. The guide emphasizes that true logical air gaps terminate sessions at an intermediary that then originates new, controlled exchanges. Real-world deployments typically combine multiple layers, such as network separation plus transport proxies plus content validation, to balance security and usability for critical environments like industrial control systems and backup repositories.

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.