<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vivekanandan Sakthivelu on foojay.io - Friends of OpenJDK</title><link>https://foojayio.github.io/website/today/author/vivekanandan-sakthivelu/</link><description>Articles written by Vivekanandan Sakthivelu on foojay.io - Friends of OpenJDK</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 12 Jun 2025 15:30:29 +0000</lastBuildDate><atom:link href="https://foojayio.github.io/website/today/author/vivekanandan-sakthivelu/index.xml" rel="self" type="application/rss+xml"/><item><title>Java Concurrency Best Practices for MongoDB</title><link>https://foojayio.github.io/website/today/java-concurrency-best-practices-for-mongodb/</link><pubDate>Thu, 12 Jun 2025 15:30:29 +0000</pubDate><guid>https://foojayio.github.io/website/today/java-concurrency-best-practices-for-mongodb/</guid><description>&lt;p&gt;In a multi-threaded, distributed environment like MongoDB, when clients execute queries concurrently, operations interleave with one another if they are not isolated, whether those operations involve single-document or multi-document operations.&lt;/p&gt;
&lt;p&gt;For instance, Client C1&amp;rsquo;s read operation might observe the effects of a write performed by Client C2, even if that write has not yet been made durable. When at least one of the concurrent operations is a write and isolation is not enforced, this can lead to undesirable outcomes, such as:&lt;/p&gt;</description></item></channel></rss>