redb 4.0 Released: XML Routes, Lazy References, Unique Keys and WS-Trust Across the Ecosystem
redb 4.0 delivers a coordinated major release across the entire ecosystem, updating redb.Core, redb.Route, redb.Tsak and redb.Identity in a single 4.0.0 version. Seventy-six NuGet packages, seven container images in GHCR and archives for Windows and Linux are now published. The Pro edition remains free and does not require a license key on the entire 4.x line.
redb.Route receives ten new packages and a substantial engine redesign. Declarative routes can now be defined in .route.xml files using the new redb.Route.Xml package and loaded into the same fluent DSL used for C# routes. The redb.Route.TestKit allows testing without brokers or route modifications through AdviceRoute, MockEndpoints and NotifyBuilder. Additional packages provide Scriban and Liquid templates, CSV, Protobuf, Avro and YAML data formats, JSONata transformations, in-memory or distributed caching, and XPath 2.0 support.
The routing engine now uses a single expression language and compiler for conditions, values and templates. New functions include stats, format, uuid and the modulo operator. The bean component allows custom objects to be used as endpoints with dependency injection. REST DSL, OpenAPI 3.0.3 generation, OpenTelemetry metrics inside routes and removal of Newtonsoft.Json in favour of System.Text.Json are also included.
Hosting improvements cover concurrent request limits with 429 responses, automatic consumer scaling for RabbitMQ, AMQP 1.0, IBM MQ, SQS and MQTT, WebSocket and SignalR support on the shared Kestrel host, and trusted proxy handling for X-Forwarded headers. Kafka consumers now preserve unprocessed records on partition revocation, and connectors for S3, Firebase and LLM providers received multiple stability and feature updates.
redb.Core introduces lazy references that load only on first access to Props when EnableLazyReferences is active, and unique keys via the new ValueUnique mechanism and [RedbUnique] attribute. Unique constraints are enforced by database indexes for scalars, nested objects, collections and entire subtrees. Schema upgrades are applied at startup with typed exceptions when rights are insufficient. CancellationToken support, save interceptors, per-request isolation levels and maintenance operations such as AnalyzeAsync are now available across PostgreSQL, MSSQL and SQLite.
redb.Tsak cluster coordination now relies on unique database keys from redb.Core. XML-only modules can be loaded and reloaded at runtime. The dashboard distinguishes load shedding from idle routes, Audit and Dead-letter pages are functional on PostgreSQL, and trusted proxy configuration is exposed for API throttling.
redb.Identity adds a WS-Trust SOAP facade supporting Issue, Validate, Cancel and Renew operations. Access tokens now include audience claims according to RFC 9068. The administrative console has been rebuilt with full pages instead of dialogs, and DPoP support behind TLS-terminating proxies has been improved.
Several security issues were addressed. Internal headers are now stripped on all three identity facades. Consent pages validate signed tickets and Origin headers. Introspection responses are restricted to token audiences. Dashboard pages require authentication with role-based access. Module signatures are verified on every load path, and the default password hasher is now bcrypt.
Clusters must be fully stopped before upgrading because mixed versions are unsupported. Large databases require a maintenance window for schema changes performed under exclusive locks. Full change logs are published at redb.ru/releases.
Related articles
Home Lab Guide: Deploying Active Directory, Windows 7 Client and ELK Stack for Security Logging
A detailed tutorial walks readers through building an isolated VirtualBox lab featuring a Windows Server 2019 domain controller with DNS and DHCP, a Windows 7 client joined to the domain, and an ELK stack running Elasticsearch, Logstash and Kibana 9.4.2. The guide covers creation of organizational units, Group Policy Objects for advanced auditing, and configuration of Winlogbeat 7.17 to forward Security, System and Application logs to Logstash. Special attention is given to common pitfalls such as missing GPO extension attributes that prevent audit policies from applying and memory constraints when running the full ELK stack on limited RAM. The author emphasizes that Windows 7 is unsupported and should only be used in isolated lab networks. All steps are provided with exact PowerShell commands, netplan configurations, and Logstash pipeline examples suitable for a 192.168.100.0/24 NAT network.
Building Your First Home Network Lab: Essential Tools and Experiments to Understand Corporate Networks
A cybersecurity professional without network knowledge resembles a guard without a building blueprint, spotting alarms but unable to trace the intruder. Setting up a personal lab on a standard computer bridges this gap through virtualization and hands-on practice with protocols and attacks. The guide recommends GNS3 for topology emulation, VirtualBox or VMware for running Windows and Linux workstations, Cisco Packet Tracer for quick simulations, Wireshark for traffic analysis, and draw.io for diagramming. Key experiments include configuring Cisco IOS routers with IP addressing, testing default gateways, observing ARP requests and replies, triggering broadcast storms via switch loops, and enabling STP to prevent loops. The lab demonstrates how legacy protocols like ARP expose networks to spoofing and why segmentation with VLANs and firewalls matters. Resources from CyberED provide demo access to courses on SOC analysis, penetration testing, and AI applications in security to extend learning.
PSLC and Agent-Ops: From Product Support to Infrastructure Transformation
Sergey Zhitinsky, founder of Git in Sky, attended the OPS Talk by Sber meetup on October 19 and discussed the PSLC methodology with architect Alexander Shapovalov. PSLC, or Product Service Lifecycle, outlines two loops for restoring services immediately and improving reliability to prevent recurrence through teams, knowledge, and platform support. Agent-Ops focuses on eight detailed steps for individual infrastructure tasks: intention, evidence collection, diagnostics, planning, approval, controlled change, verification, and lessons learned. The article illustrates their complementary use in a scenario where post-release log growth fills a database disk, requiring both service restoration and root-cause fixes. Both approaches emphasize knowledge retention, action control, and human accountability, though Agent-Ops v0.5.1 mandates explicit human approval and separate execution for production changes. PSLC suits larger organizations with shared platforms, while Agent-Ops targets smaller teams handling infrastructure operations with AI agents.
Russian Organizations Allocate 4.5 Trillion Rubles to Innovation Spending in 2025
Large and medium-sized Russian organizations directed a total of 4.5 trillion rubles toward innovation activities during 2025. Nearly half of the expenditure originated from the services sector, while information technology and telecommunications accounted for 860.9 billion rubles. The Institute for Statistical Studies and Economics of Knowledge at HSE University published the figures based on Rosstat data, showing an innovation intensity rate of 2.7 percent. Services companies alone contributed approximately 2.3 trillion rubles, including 882.7 billion rubles for research and development. Astra Group IR Director Vladislav Anshakov outlined major spending areas such as product development, cloud and AI hardware, and acquisitions of technologies and teams. The group expanded its portfolio with the Perseus DBMS and a 26 percent stake in AI developer AIB. More than one-third of organizations cited high costs and insufficient internal funds as key barriers to further innovation.