DORI: A Distributed Observation and Reconciliation Interface for Resilient Multi-Source Event Synchronization in Cloud-Native Systems
This paper presents DORI, a distributed interface that ensures resilient multi-source event synchronization in cloud-native systems by applying reconciliation-by-design principles to detect inconsistencies, validate blockchain events, and provide idempotent corrections before atomically delivering them to downstream microservices.
Original paper licensed under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
In the modern digital world, two distinct layers of technology are increasingly trying to work together, often with friction. On one side sits the traditional internet, where businesses run on fast, centralized servers that can instantly update records and handle millions of requests. On the other side is the newer world of blockchain, a system where transactions are recorded on a public, shared ledger that is incredibly secure but slower and more complex. When companies try to build applications that use both, they face a difficult problem: the blockchain might say a transaction happened, but the traditional servers might not see it immediately, or they might see it twice, or in the wrong order. If a bank or a hospital relies on these systems to manage money or patient records, such confusion can lead to lost funds, duplicate treatments, or broken trust. The core challenge is not just connecting the two worlds, but ensuring that the information flowing between them is accurate, consistent, and reliable, even when the connection is shaky or the data arrives late.
Researchers have developed a new system called DORI to solve this specific problem of keeping these two worlds in sync. The team, comprising engineers and academics from institutions in Bangladesh, the United States, and Norway, designed a bridge that sits between the blockchain and the cloud-based services that run everyday applications. Instead of blindly trusting a single signal from the blockchain, DORI acts as a careful gatekeeper. It listens to the blockchain through multiple different channels at the same time. If one channel says a transaction happened and another says it did not, the system waits. It does not rush to update the business records until it has gathered enough evidence from different sources to be sure the event is real and permanent. This approach prevents the chaos that occurs when different parts of a system operate on different versions of the truth.
The researchers built a working prototype of this system to see how it would perform under pressure. They set up a test environment that mimicked a real-world scenario where a blockchain network, specifically the Ethereum Sepolia test network, was sending out thousands of transaction updates. These updates were then fed into a cloud-based system that needed to process them for things like managing user accounts or tracking digital assets. To ensure the system was robust, the researchers did not rely on just one way of watching the blockchain. They used two different types of observers: one that listened for events as they happened in real-time, and another that checked a historical index of past events to fill in any gaps. This dual approach meant that if the real-time connection dropped or was delayed, the system could still recover the missing information from the historical index.
When the team tested the system with a heavy load of 1,800 transactions, the results showed that the bridge worked effectively. The system successfully synchronized the blockchain events with the downstream cloud services in 97.1% of cases. This high success rate is significant because it demonstrates that the system can handle the messy reality of network delays and data inconsistencies without losing track of important events. The researchers also found that the two different observation methods had their own strengths. The real-time listener was faster, responding in about 0.146 seconds on average, while the historical index was slightly slower but handled a higher volume of requests per second. By combining both, the system achieved a balance between speed and reliability, ensuring that no event was missed even if one source faltered.
A critical part of DORI's design is how it handles mistakes. In a blockchain, the order of transactions can sometimes change if the network reorganizes its history, a process that can invalidate a transaction that was previously thought to be final. Traditional systems might treat a confirmed event as permanent and never look back, which could leave a business with incorrect data if the blockchain later changes its mind. DORI, however, treats every event as a living record that can be updated. If a transaction is admitted into the system and then later found to be invalid due to a network change, DORI does not delete the record. Instead, it creates a new, corrected version of that record that links back to the original. This allows the system to fix errors without erasing the history of what happened, providing a clear and auditable trail that shows exactly how a decision was made and how it was later corrected.
The researchers also paid close attention to privacy and security. In many industries, such as finance and healthcare, regulations require that sensitive personal data be kept private, even while maintaining a record of transactions. DORI addresses this by separating the public proof of a transaction from the private details. The system records a unique, unchangeable code that proves an event happened, but it keeps the actual names and private details in a secure, off-chain storage that can be controlled and deleted according to privacy laws. This means that auditors can verify that a transaction occurred and trace its path through the system without ever seeing the sensitive personal information attached to it. This design allows organizations to meet strict legal requirements for data protection while still maintaining the transparency needed for secure operations.
The study concludes that this method of coordinating events is a viable way to build reliable applications that span both blockchain and traditional cloud systems. The team demonstrated that by using a "resilience-by-design" approach, where the system is built to expect and handle failures rather than assuming everything will work perfectly, they could create a stable environment for complex digital interactions. The prototype proved that it is possible to reconcile conflicting data from multiple sources, recover from network interruptions, and correct past errors without breaking the flow of business operations. While the system is not a magic solution that eliminates all risks, it provides a structured, proven way to manage the uncertainty inherent in connecting decentralized networks with centralized services. The findings suggest that with the right coordination layer, the promise of hybrid applications can be realized without sacrificing the dependability that modern businesses require.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.