<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Concurrency on UberMongoose</title>
		<link>http://localhost:1313/tags/concurrency/</link>
		<description>Recent content in Concurrency on UberMongoose</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sun, 15 Dec 2013 07:20:02 +0530</lastBuildDate>
		
			<atom:link href="http://localhost:1313/tags/concurrency/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Pessimistic vs Optimistic Concurrency</title>
				<link>http://localhost:1313/post/pessimistic-vs-optimistic-concurrency/</link>
				<pubDate>Sun, 15 Dec 2013 07:20:02 +0530</pubDate>
				<guid>http://localhost:1313/post/pessimistic-vs-optimistic-concurrency/</guid>
				<description>&lt;p&gt;Concurrency is when multiple jobs see incremental progress within the same time period. It may be that the concurrency is parallel where both jobs progress together at the same time or time sliced wherein parts of both jobs are done one after the other by a single processor. Whichever the case concurrency creates problems for shared resources. When there is only one job executing at a given point in time the resource can be viewed as consistent on any access. However when there is more than one job executing then care must be taken to ensure that the resource is consistent across both jobs. Consider the classic example of 2 jobs which both increment a single counter.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
