Comments on: Storing Images inside Databases http://maxtheitpro.com/storing-images-inside-databases Max explores the world of IT, Music, Travel & other stuff... Fri, 03 Sep 2010 18:17:51 -0500 http://wordpress.org/?v=2.8.4 hourly 1 By: Maxwell http://maxtheitpro.com/storing-images-inside-databases/comment-page-1#comment-322 Maxwell Wed, 05 Jul 2006 06:17:00 +0000 http://maxtheitpro.com/storing-images-inside-databases#comment-322 Steve, thanks for the great post. I completely agree with you about handling static images in some sort of RAM cache. I was referring to images that are uploaded by users/sellers in order to sell their products (Real Estate listings, Cars, Clothing, etc.). So, in this regard, what would you suggest?<br/><br/>To answer your question, we ONLY use the LAMP (Linux, Apache, MySQL, PHP) stack. I got into server-side development with SQL Server, Sybase and ASP on Windows NT when I was doing my internship at the Bank of Montreal in TDot (Toronto).<br/><br/>Oh, thanks for the Dylan Drazen links in your other post. I've heard 1 or 2 of his mixes. His style is amazing...always upbeat. Steve, thanks for the great post. I completely agree with you about handling static images in some sort of RAM cache. I was referring to images that are uploaded by users/sellers in order to sell their products (Real Estate listings, Cars, Clothing, etc.). So, in this regard, what would you suggest?

To answer your question, we ONLY use the LAMP (Linux, Apache, MySQL, PHP) stack. I got into server-side development with SQL Server, Sybase and ASP on Windows NT when I was doing my internship at the Bank of Montreal in TDot (Toronto).

Oh, thanks for the Dylan Drazen links in your other post. I’ve heard 1 or 2 of his mixes. His style is amazing…always upbeat.

]]> By: Ntwiga http://maxtheitpro.com/storing-images-inside-databases/comment-page-1#comment-320 Ntwiga Wed, 05 Jul 2006 02:20:00 +0000 http://maxtheitpro.com/storing-images-inside-databases#comment-320 Neither appraoch is workable in real life high traffic website. Disk or database are both too "slow: to be used for static site content. With a good hosting company, static branding images would ideally be cached in RAM on the webserver as they are a component of every single page.<br/><br/>The idea is that the files/images (stuff like style sheets, branding images etc etc gets read once into system RAM (which is the fastest memory available) when the web server start and is never read again (of course, in reality, there are mechanisms to force the web server to refresh the data from disk).As developers though, you should not assume that your hosting company will implement this for you and should act proactively to make sure it happens.<br/><br/><a HREF="http://www.microsoft.com/technet/prodtechnol/windows2000serv/technologies/iis/deploy/rollout/websrvbp.mspx" REL="nofollow" TITLE="">Read this for some more insights into this</a>.<br/><br/>A question for you if I may, your posts seem to imply that you chose to build a php application using SQLServer for the DB. Any particular reason why you chose this for a stack rather than the standard (and free!!) php/apache/mysql stack?<br/><br/><br/>- Steve Neither appraoch is workable in real life high traffic website. Disk or database are both too “slow: to be used for static site content. With a good hosting company, static branding images would ideally be cached in RAM on the webserver as they are a component of every single page.

The idea is that the files/images (stuff like style sheets, branding images etc etc gets read once into system RAM (which is the fastest memory available) when the web server start and is never read again (of course, in reality, there are mechanisms to force the web server to refresh the data from disk).As developers though, you should not assume that your hosting company will implement this for you and should act proactively to make sure it happens.

Read this for some more insights into this.

A question for you if I may, your posts seem to imply that you chose to build a php application using SQLServer for the DB. Any particular reason why you chose this for a stack rather than the standard (and free!!) php/apache/mysql stack?

- Steve

]]> By: Anonymous http://maxtheitpro.com/storing-images-inside-databases/comment-page-1#comment-314 Anonymous Fri, 05 May 2006 05:43:00 +0000 http://maxtheitpro.com/storing-images-inside-databases#comment-314 This is valuble info that i was serching for. Max what about if your site gets lots of trafic? How would this affect database performance? This is valuble info that i was serching for. Max what about if your site gets lots of trafic? How would this affect database performance?

]]>