<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Storage on about:rileycsillag fka drewcsillag</title>
		<link>https://riley.thecsillags.com/categories/storage/</link>
		<description>Recent content in Storage on about:rileycsillag fka drewcsillag</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 25 May 2015 12:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://riley.thecsillags.com/categories/storage/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Storage System Design Considerations</title>
				<link>https://riley.thecsillags.com/posts/2015-05-25-storage-system-design-part-1/</link>
				<pubDate>Mon, 25 May 2015 12:00:00 +0000</pubDate>
				<guid>https://riley.thecsillags.com/posts/2015-05-25-storage-system-design-part-1/</guid>
				<description>&lt;p&gt;When designing storage systems for applications, not building&#xA;something like a SQL/NoSQL database, I&amp;rsquo;m talking the layer/logic that&#xA;goes on top, you have to consider a whole bunch of things if you want&#xA;to build the &amp;ldquo;right thing(TM)&amp;rdquo; for your application.&lt;/p&gt;&#xA;&lt;p&gt;In part one, we&amp;rsquo;ll be considering the simple cases (spoiler: most&#xA;cases are simple) and SQL databases, in part 2 we&amp;rsquo;ll be&#xA;considering NoSQL databases.&lt;/p&gt;&#xA;&lt;!-- more --&gt;&#xA;&lt;p&gt;Even with various considerations to think about, hard and fast rules&#xA;about datastores tend to get very difficult, as the various&#xA;considerations can push things around quite a bit as to how to best&#xA;implement them for today while taking tomorrow into account.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
