<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Distributed Systems on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/tags/distributed-systems/</link><description>Recent content in Distributed Systems on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 28 Oct 2025 07:00:01 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/tags/distributed-systems/index.xml" rel="self" type="application/rss+xml"/><item><title>Dynamic consistency boundaries</title><link>https://javapro-en.svenruppert.com/dynamic-consistency-boundaries/</link><pubDate>Tue, 28 Oct 2025 07:00:01 +0000</pubDate><guid>https://javapro-en.svenruppert.com/dynamic-consistency-boundaries/</guid><description>&lt;p&gt;In software, Consistency may refer to many things - Code Consistency, Data Consistency, User Interface Consistency, etc. In this article, I am focusing on Data Consistency. Simply put, Data Consistency ensures that data remains accurate and reliable across different parts of a system. More formally, Data Consistency is one of the Database Transaction properties (ACID^(&lt;a href="#01a8d66d-6749-455b-bbf6-a3934138f30b"&gt;1&lt;/a&gt;)) defined as:&lt;/p&gt;
&lt;blockquote class="pullquote"&gt;
 &lt;span class="pullquote-mark" aria-hidden="true"&gt;“&lt;/span&gt;
 &lt;div class="pullquote-body"&gt;&lt;p&gt;Consistency (or correctness) ensures that a transaction can only bring the database from one consistent state to another, preserving database invariants.&lt;/p&gt;</description></item></channel></rss>