<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Choosing a non-relational database; why we migrated from MySQL to MongoDB</title>
	<atom:link href="http://blog.boxedice.com/2009/07/25/choosing-a-non-relational-database-why-we-migrated-from-mysql-to-mongodb/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.boxedice.com/2009/07/25/choosing-a-non-relational-database-why-we-migrated-from-mysql-to-mongodb/</link>
	<description>Real software development</description>
	<lastBuildDate>Thu, 11 Mar 2010 16:59:41 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Bryan Migliorisi</title>
		<link>http://blog.boxedice.com/2009/07/25/choosing-a-non-relational-database-why-we-migrated-from-mysql-to-mongodb/#comment-844</link>
		<dc:creator>Bryan Migliorisi</dc:creator>
		<pubDate>Thu, 04 Mar 2010 20:36:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.boxedice.com/?p=314#comment-844</guid>
		<description>Thanks - and thanks for the follow up too :)</description>
		<content:encoded><![CDATA[<p>Thanks &#8211; and thanks for the follow up too :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Notes from a production MongoDB deployment &#171; Monterail Devblog</title>
		<link>http://blog.boxedice.com/2009/07/25/choosing-a-non-relational-database-why-we-migrated-from-mysql-to-mongodb/#comment-841</link>
		<dc:creator>Notes from a production MongoDB deployment &#171; Monterail Devblog</dc:creator>
		<pubDate>Thu, 04 Mar 2010 20:04:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.boxedice.com/?p=314#comment-841</guid>
		<description>[...] in July last year I wrote about our migration from MySQL to MongoDB. We have been running MongoDB in production for our server monitoring service, Server Density, [...]</description>
		<content:encoded><![CDATA[<p>[...] in July last year I wrote about our migration from MySQL to MongoDB. We have been running MongoDB in production for our server monitoring service, Server Density, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Caffeine Driven Development &#187; Blog Archive &#187; L33t Links #83</title>
		<link>http://blog.boxedice.com/2009/07/25/choosing-a-non-relational-database-why-we-migrated-from-mysql-to-mongodb/#comment-835</link>
		<dc:creator>Caffeine Driven Development &#187; Blog Archive &#187; L33t Links #83</dc:creator>
		<pubDate>Tue, 02 Mar 2010 08:13:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.boxedice.com/?p=314#comment-835</guid>
		<description>[...] Choosing a non-relational database; why we migrated from MySQL to MongoDB and Notes from a production MongoDB deployment, from BoxedIce [...]</description>
		<content:encoded><![CDATA[<p>[...] Choosing a non-relational database; why we migrated from MySQL to MongoDB and Notes from a production MongoDB deployment, from BoxedIce [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Living Cosmos &#187; Blog Archive &#187; Choosing a non-relational database; why we migrated from MySQL to MongoDB « Boxed Ice Blog</title>
		<link>http://blog.boxedice.com/2009/07/25/choosing-a-non-relational-database-why-we-migrated-from-mysql-to-mongodb/#comment-809</link>
		<dc:creator>Living Cosmos &#187; Blog Archive &#187; Choosing a non-relational database; why we migrated from MySQL to MongoDB « Boxed Ice Blog</dc:creator>
		<pubDate>Mon, 01 Mar 2010 00:19:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.boxedice.com/?p=314#comment-809</guid>
		<description>[...] Choosing a non-relational database; why we migrated from MySQL to MongoDB « Boxed Ice Blog. [...]</description>
		<content:encoded><![CDATA[<p>[...] Choosing a non-relational database; why we migrated from MySQL to MongoDB « Boxed Ice Blog. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Notes from a production MongoDB deployment &#171; Boxed Ice Blog</title>
		<link>http://blog.boxedice.com/2009/07/25/choosing-a-non-relational-database-why-we-migrated-from-mysql-to-mongodb/#comment-795</link>
		<dc:creator>Notes from a production MongoDB deployment &#171; Boxed Ice Blog</dc:creator>
		<pubDate>Sun, 28 Feb 2010 18:44:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.boxedice.com/?p=314#comment-795</guid>
		<description>[...] in July last year I wrote about our migration from MySQL to MongoDB. We have been running MongoDB in production for our server monitoring service, Server Density, [...]</description>
		<content:encoded><![CDATA[<p>[...] in July last year I wrote about our migration from MySQL to MongoDB. We have been running MongoDB in production for our server monitoring service, Server Density, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nicht-relationale Datenpersistenz in Java mit MongoDB &#124; SemanticBlog</title>
		<link>http://blog.boxedice.com/2009/07/25/choosing-a-non-relational-database-why-we-migrated-from-mysql-to-mongodb/#comment-790</link>
		<dc:creator>Nicht-relationale Datenpersistenz in Java mit MongoDB &#124; SemanticBlog</dc:creator>
		<pubDate>Sat, 27 Feb 2010 10:19:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.boxedice.com/?p=314#comment-790</guid>
		<description>[...] Choosing a non relational database why we migrated from mysql tomongodb [...]</description>
		<content:encoded><![CDATA[<p>[...] Choosing a non relational database why we migrated from mysql tomongodb [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Mytton</title>
		<link>http://blog.boxedice.com/2009/07/25/choosing-a-non-relational-database-why-we-migrated-from-mysql-to-mongodb/#comment-785</link>
		<dc:creator>David Mytton</dc:creator>
		<pubDate>Fri, 26 Feb 2010 17:06:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.boxedice.com/?p=314#comment-785</guid>
		<description>Such as?</description>
		<content:encoded><![CDATA[<p>Such as?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Quinlan</title>
		<link>http://blog.boxedice.com/2009/07/25/choosing-a-non-relational-database-why-we-migrated-from-mysql-to-mongodb/#comment-784</link>
		<dc:creator>Matthew Quinlan</dc:creator>
		<pubDate>Fri, 26 Feb 2010 16:48:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.boxedice.com/?p=314#comment-784</guid>
		<description>Thanks for sharing your experience.  I am a little surprised at the choice to move to a non-relational database based on the specific issues you identified with MySQL.   Did you consider using a better relational database that did not suffer from those weaknesses?  I ask because there are many very good RDBMSs that could have addressed those issues without requiring you to completely re-architect your application.  Just curious.</description>
		<content:encoded><![CDATA[<p>Thanks for sharing your experience.  I am a little surprised at the choice to move to a non-relational database based on the specific issues you identified with MySQL.   Did you consider using a better relational database that did not suffer from those weaknesses?  I ask because there are many very good RDBMSs that could have addressed those issues without requiring you to completely re-architect your application.  Just curious.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Mytton</title>
		<link>http://blog.boxedice.com/2009/07/25/choosing-a-non-relational-database-why-we-migrated-from-mysql-to-mongodb/#comment-775</link>
		<dc:creator>David Mytton</dc:creator>
		<pubDate>Thu, 18 Feb 2010 23:33:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.boxedice.com/?p=314#comment-775</guid>
		<description>We&#039;ve learned a fair bit about the best way to run MongoDB, but mostly around dealing with large data sets. Our primary database is currently just under 800GB. The most important thing is there is no single server durability - you must use replication across data centres. See http://blog.mongodb.org/post/381927266/what-about-durability</description>
		<content:encoded><![CDATA[<p>We&#8217;ve learned a fair bit about the best way to run MongoDB, but mostly around dealing with large data sets. Our primary database is currently just under 800GB. The most important thing is there is no single server durability &#8211; you must use replication across data centres. See <a href="http://blog.mongodb.org/post/381927266/what-about-durability" rel="nofollow">http://blog.mongodb.org/post/381927266/what-about-durability</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryan Migliorisi</title>
		<link>http://blog.boxedice.com/2009/07/25/choosing-a-non-relational-database-why-we-migrated-from-mysql-to-mongodb/#comment-772</link>
		<dc:creator>Bryan Migliorisi</dc:creator>
		<pubDate>Thu, 18 Feb 2010 19:45:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.boxedice.com/?p=314#comment-772</guid>
		<description>Great article David.

Since posting this, do you have any additional thoughts to share?  I am working on a project where we have decided to use MongoDB and I am also looking to use it side by side with a very large MySQL db on another project.  

Since your post is around 6 months old, I was wondering if you have learned anything new?  I know that the MongoDB dev team is very active and has been working on a lot of new features and bug fixes.</description>
		<content:encoded><![CDATA[<p>Great article David.</p>
<p>Since posting this, do you have any additional thoughts to share?  I am working on a project where we have decided to use MongoDB and I am also looking to use it side by side with a very large MySQL db on another project.  </p>
<p>Since your post is around 6 months old, I was wondering if you have learned anything new?  I know that the MongoDB dev team is very active and has been working on a lot of new features and bug fixes.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
