<?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/"
	>
<channel>
	<title>Comments on: Part one: Storing images in Oracle with ColdFusion</title>
	<atom:link href="http://blog.sixsigns.com/2006/02/16/part-one-storing-images-in-oracle-with-coldfusion/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sixsigns.com/2006/02/16/part-one-storing-images-in-oracle-with-coldfusion/</link>
	<description>Enrich people's lives and web experience</description>
	<pubDate>Wed, 07 Jan 2009 14:22:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Nitai Aventaggiato</title>
		<link>http://blog.sixsigns.com/2006/02/16/part-one-storing-images-in-oracle-with-coldfusion/comment-page-1/#comment-123</link>
		<dc:creator>Nitai Aventaggiato</dc:creator>
		<pubDate>Thu, 30 Mar 2006 08:43:23 +0000</pubDate>
		<guid isPermaLink="false">http://wp.econtentpark.com/2006/02/16/Part-one:-Storing-images-in-Oracle-with-ColdFusion#comment-123</guid>
		<description>Hi Mitch&lt;br /&gt;&lt;br /&gt;Yes, I am going to write a part two of this. I just haven't had time to do so. We are currently very busy with finishing up our Digital Asset Management &#34;eContentPark&#34;. There is the biggest IT Trade Show taking place in Mai here in Switzerland and we are releasing then eContentPark for free to the public.&lt;br /&gt;&lt;br /&gt;I do recommend storing images in the database for a couple of reasons. Some of these are:&lt;br /&gt;
&lt;ol&gt;
    &lt;li&gt;Having them all in the database makes it very easy to manage them. If you are just working with 100 images no problem, but what is if you work with a million images?&lt;/li&gt;
    &lt;li&gt;You just need to backup the database. Also for recovering this is a straight forward process. We have had to move a million images in the past for some customers (which stored everyhting in the filesystem). It took a long time to compress them and the move them and so on. Some information was even lost during the process (IPTC, XMP) because of the OS switch (from Windows to Linux and vice versa). I am not saying that this is the case all the time, but I have seen it in several occassions.&lt;/li&gt;
    &lt;li&gt;Security: Everyone with access to the server can manipulate and get the images, but within a database you can restrict who can do what. You can even go as far as to modify the URL to the images in such a way that one simply can't get the images without going trough your application (or alike).&lt;/li&gt;
    &lt;li&gt;Some people might say that storing images in the database is a big performance hit. This argument might have been true in the past, but with today's cheap Ram and Disk Drive prices it is very easy to get a good running server up in no time. I recommend to have a dedicated machine for Oracle alone with at least 6 GB of Ram.&lt;/li&gt;
    &lt;li&gt;When you store images in the file system and someone removes the image, the whole database gets out of sync. Order purchases are messed up, customers complaining and so on. This (should) not happen if you have them in the database.&lt;/li&gt;
&lt;/ol&gt;
These are just some thoughts. I am sure there are more pro and cons to storing images in the database. We have developed another digital asset management solution in the past which stored images in the filesystem. Performance was the same as in the database and we have had problems with data being out of sync, security and some other things.&lt;br /&gt;&lt;br /&gt;I can only speak of storing images in the Oracle database, because this is the only database I have found which has modules (like Intermedia) especially for images or media in general for that matter.&lt;br /&gt;&lt;br /&gt;I hope this helps. If you have any further questions or comments please let me know.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start -->Hi Mitch</p>
<p>Yes, I am going to write a part two of this. I just haven&#8217;t had time to do so. We are currently very busy with finishing up our Digital Asset Management &quot;eContentPark&quot;. There is the biggest IT Trade Show taking place in Mai here in Switzerland and we are releasing then eContentPark for free to the public.</p>
<p>I do recommend storing images in the database for a couple of reasons. Some of these are:</p>
<ol>
<li>Having them all in the database makes it very easy to manage them. If you are just working with 100 images no problem, but what is if you work with a million images?</li>
<li>You just need to backup the database. Also for recovering this is a straight forward process. We have had to move a million images in the past for some customers (which stored everyhting in the filesystem). It took a long time to compress them and the move them and so on. Some information was even lost during the process (IPTC, XMP) because of the OS switch (from Windows to Linux and vice versa). I am not saying that this is the case all the time, but I have seen it in several occassions.</li>
<li>Security: Everyone with access to the server can manipulate and get the images, but within a database you can restrict who can do what. You can even go as far as to modify the URL to the images in such a way that one simply can&#8217;t get the images without going trough your application (or alike).</li>
<li>Some people might say that storing images in the database is a big performance hit. This argument might have been true in the past, but with today&#8217;s cheap Ram and Disk Drive prices it is very easy to get a good running server up in no time. I recommend to have a dedicated machine for Oracle alone with at least 6 GB of Ram.</li>
<li>When you store images in the file system and someone removes the image, the whole database gets out of sync. Order purchases are messed up, customers complaining and so on. This (should) not happen if you have them in the database.</li>
</ol>
<p>These are just some thoughts. I am sure there are more pro and cons to storing images in the database. We have developed another digital asset management solution in the past which stored images in the filesystem. Performance was the same as in the database and we have had problems with data being out of sync, security and some other things.</p>
<p>I can only speak of storing images in the Oracle database, because this is the only database I have found which has modules (like Intermedia) especially for images or media in general for that matter.</p>
<p>I hope this helps. If you have any further questions or comments please let me know.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mitch</title>
		<link>http://blog.sixsigns.com/2006/02/16/part-one-storing-images-in-oracle-with-coldfusion/comment-page-1/#comment-122</link>
		<dc:creator>Mitch</dc:creator>
		<pubDate>Thu, 30 Mar 2006 01:07:50 +0000</pubDate>
		<guid isPermaLink="false">http://wp.econtentpark.com/2006/02/16/Part-one:-Storing-images-in-Oracle-with-ColdFusion#comment-122</guid>
		<description>Are you going to write part 2 of this article? Do you recommend storing images in Oracle vs. storing images on disk?</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start -->Are you going to write part 2 of this article? Do you recommend storing images in Oracle vs. storing images on disk?<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
</channel>
</rss>
