Why standard IT uptime and rollback logic fails in industrial control systems

·1 views

Industrial control systems operate under fundamentally different reliability rules than web services, where a brief outage can mean scrapped batches, damaged equipment, or even safety incidents. Unlike web apps, physical processes such as cement kilns or water treatment plants do not pause during a software rollback, making mid-process recovery far more complex and potentially dangerous. Restoring an older software version to a changed physical state — with altered temperatures, pressures, or chemical compositions — can be riskier than completing a flawed deployment. This is why industrial environments enforce strict change management protocols, including planned maintenance windows and operator sign-offs, which may appear bureaucratic to IT teams but reflect real-world physical constraints. Developers building software for operational technology must design explicitly for safe manual handoffs, test against physical failure scenarios, and consult plant operators who understand undocumented failure modes.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

How WebSockets Enable Real-Time BTC to USD and BRL Conversion

Polling APIs every few seconds is often insufficient for real-time Bitcoin price conversion, making WebSockets a more efficient alternative. WebSockets maintain a single open connection, delivering price updates instantly with lower latency and fewer HTTP requests. A common approach streams BTC/USD and USD/BRL pairs separately, then calculates BTC/BRL by multiplying the two rates. Incoming data is normalized into a consistent internal format called a MarketTick, keeping business logic independent of external data providers. A BtcConverter class stores the latest rates and produces a conversion snapshot — a stable, computed output object consumed by the UI or other services.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How Metadata Filtering and Reranking Improve RAG Search Accuracy

Retrieval-Augmented Generation (RAG) systems typically use vector similarity search to find relevant document chunks, but this approach can be slow and imprecise at scale. Metadata filtering addresses this by narrowing the search space using stored attributes like chapter name or author before running vector comparisons, and is natively supported by databases such as Pinecone, ChromaDB, and Qdrant. Even after retrieval, the closest vectors do not always represent the most contextually relevant documents, which is where reranking comes in. A cross-encoder model takes both the user query and each retrieved document as joint input, assigning relevance scores that reorder results by actual semantic match rather than vector proximity. Reranking is particularly valuable for multimodal content, such as images, where surface-level similarity may otherwise surface less relevant results.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Kiponos Java SDK 5.0 Released with Three-Mode Reliability System and Folder API

Kiponos has released Java SDK version 5.0.0.260710 on Maven Central on July 12, 2026, under the group ID io.kiponos. The update introduces a three-mode state pattern — Ready, Offline, and Safe — that switches internally behind a stable facade, shielding application code from direct mode exposure. In Ready mode the SDK serves live configuration data, while Offline mode provides read-only access to a Last Known Good snapshot when the hub is unreachable, and Safe mode fails closed without overwriting that snapshot. The release also formalises a Folder API, allowing developers to navigate hierarchical configuration trees and retrieve typed values using methods such as getInt and path. Developers can migrate by switching to the sdk-boot-3 artifact, with sdk-boot-2 remaining available for legacy Spring Boot 2 projects.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

x402 Agent Payment Protocol Gains Backers but Lacks Independent Security Verification

The Linux Foundation has launched the x402 Foundation around an AI agent payment protocol originally developed by Coinbase, Cloudflare, and Stripe, with major firms including Google, AWS, Visa, and Mastercard expressing early support. The protocol is being positioned as an 'SSL for AI commerce,' standardizing how AI agents authenticate and complete payments. While x402 has a working specification and growing interoperability support, analysts note it still lacks a normative adversarial security testing suite that all participants must pass. A key unresolved gap is the absence of an independent assurance layer — meaning the party that runs a security check currently cannot be independently verified by a separate party. Experts argue that until payment execution evidence and security assurance evidence are formally separated, contested transactions cannot be reliably audited or reproduced.

0 comments Read more at DEV Community