<?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: Should All New Sites Have Backend Systems?</title>
	<atom:link href="http://blog.websitestyle.com/index.php/2006/12/03/should-all-new-sites-have-backend-systems/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.websitestyle.com/index.php/2006/12/03/should-all-new-sites-have-backend-systems/</link>
	<description>Various Epiphanies of a Technical Mind</description>
	<lastBuildDate>Sun, 29 Jan 2012 23:20:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Brandon J. Deboer</title>
		<link>http://blog.websitestyle.com/index.php/2006/12/03/should-all-new-sites-have-backend-systems/comment-page-1/#comment-68561</link>
		<dc:creator>Brandon J. Deboer</dc:creator>
		<pubDate>Thu, 09 Apr 2009 21:29:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.websitestyle.com/?p=170#comment-68561</guid>
		<description>Hello sorry about our previous posts.

I do believe as well Certain websites need backend systems.

I say certain sites because well you have to look at it as how many times are they going to be updating their content how many pages factor in with the website ?

There are many questions to be asked when dealing with CMS - &quot;Content Management Systems&quot; with our clients we like to always offer a CMS solution to them for easy and functional updating of their of their web content.

Now if a customer comes to us and they have say a three page website/webpage or promotional website depending on the size of content we will offer them a maintenance solution that way its a simple solution for the user to get their content updated.

Or if we have a big project 10,000 + pages we will set the client up with a CMS either we take care of the content from our end or someone on their marketing or IT department will keep the content updated.

So really the main question is what they need and when they need it.

I recommend CMS myself for any Web solution online as long as the project or website is at least over 5 pages then its a recommendation.

Well thats my final word on Content Management Systems.

This is a well needed Article good job.</description>
		<content:encoded><![CDATA[<p>Hello sorry about our previous posts.</p>
<p>I do believe as well Certain websites need backend systems.</p>
<p>I say certain sites because well you have to look at it as how many times are they going to be updating their content how many pages factor in with the website ?</p>
<p>There are many questions to be asked when dealing with CMS &#8211; &#8220;Content Management Systems&#8221; with our clients we like to always offer a CMS solution to them for easy and functional updating of their of their web content.</p>
<p>Now if a customer comes to us and they have say a three page website/webpage or promotional website depending on the size of content we will offer them a maintenance solution that way its a simple solution for the user to get their content updated.</p>
<p>Or if we have a big project 10,000 + pages we will set the client up with a CMS either we take care of the content from our end or someone on their marketing or IT department will keep the content updated.</p>
<p>So really the main question is what they need and when they need it.</p>
<p>I recommend CMS myself for any Web solution online as long as the project or website is at least over 5 pages then its a recommendation.</p>
<p>Well thats my final word on Content Management Systems.</p>
<p>This is a well needed Article good job.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon J. Deboer</title>
		<link>http://blog.websitestyle.com/index.php/2006/12/03/should-all-new-sites-have-backend-systems/comment-page-1/#comment-66844</link>
		<dc:creator>Brandon J. Deboer</dc:creator>
		<pubDate>Sat, 21 Mar 2009 02:14:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.websitestyle.com/?p=170#comment-66844</guid>
		<description>All I can say is my company does not work on Computer Systems we are a Web development firm in Canada.</description>
		<content:encoded><![CDATA[<p>All I can say is my company does not work on Computer Systems we are a Web development firm in Canada.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nicole</title>
		<link>http://blog.websitestyle.com/index.php/2006/12/03/should-all-new-sites-have-backend-systems/comment-page-1/#comment-65832</link>
		<dc:creator>Nicole</dc:creator>
		<pubDate>Wed, 11 Mar 2009 07:01:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.websitestyle.com/?p=170#comment-65832</guid>
		<description>@Brandon

While that was a lovely general definition, it sounds like something you&#039;d read on &lt;strike&gt;Wikipedia&lt;/strike&gt; Webster in the wording. If it&#039;s how you phrase things for your business website, might I suggest making it more simple for the general reader to understand.

Beyond that, the scope of the article was not as open as your description. In fact, I began by saying the following: &lt;blockquote&gt;But before I get into the discussion, let me define what (for these purposes) we’re considering a &#039;backend system&#039;:&quot;&lt;/blockquote&gt;
At which point I went on to define that we were talking about a variant of Content Management System.

Of course, if you&#039;re going to use example of software in your description of a backend, you may want to open that up a little more to open source since I heavily write about CMS backends that run on LAMP and quite a few articles on Linux. The reason for that is not only my experience that has lead me to make those choices, but also the fact that my readers are interested in LAMP setups. I&#039;d estimate that 80% or more of my readers use a LAMP core for their websites.I do not, ever, ever, suggest the use of a Microsoft product to secure their servers.

That said, best of luck to you in your computer system business, and feel free to comment from a &#039;Microsoft shop&#039; perspective on any articles if you like. It&#039;s always good to have two points of view and I&#039;m openly biased since I used to create systems using MS products.</description>
		<content:encoded><![CDATA[<p>@Brandon</p>
<p>While that was a lovely general definition, it sounds like something you&#8217;d read on <strike>Wikipedia</strike> Webster in the wording. If it&#8217;s how you phrase things for your business website, might I suggest making it more simple for the general reader to understand.</p>
<p>Beyond that, the scope of the article was not as open as your description. In fact, I began by saying the following:<br />
<blockquote>But before I get into the discussion, let me define what (for these purposes) we’re considering a &#8216;backend system&#8217;:&#8221;</p></blockquote>
<p>At which point I went on to define that we were talking about a variant of Content Management System.</p>
<p>Of course, if you&#8217;re going to use example of software in your description of a backend, you may want to open that up a little more to open source since I heavily write about CMS backends that run on LAMP and quite a few articles on Linux. The reason for that is not only my experience that has lead me to make those choices, but also the fact that my readers are interested in LAMP setups. I&#8217;d estimate that 80% or more of my readers use a LAMP core for their websites.I do not, ever, ever, suggest the use of a Microsoft product to secure their servers.</p>
<p>That said, best of luck to you in your computer system business, and feel free to comment from a &#8216;Microsoft shop&#8217; perspective on any articles if you like. It&#8217;s always good to have two points of view and I&#8217;m openly biased since I used to create systems using MS products.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon J. Deboer</title>
		<link>http://blog.websitestyle.com/index.php/2006/12/03/should-all-new-sites-have-backend-systems/comment-page-1/#comment-65830</link>
		<dc:creator>Brandon J. Deboer</dc:creator>
		<pubDate>Wed, 11 Mar 2009 06:39:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.websitestyle.com/?p=170#comment-65830</guid>
		<description>&quot;Back-end systems&quot; loosely refers to servers, superservers, clustered systems, midrange systems, and mainframes that provide data services to users. The location of these services is often called the server farm or data center.

The server in client/server refers to the back-end systems. Client/server computing splits processing between a front-end application that runs on the client&#039;s workstation, and back-end services. Typical back-end services include database management systems (DBMSs), messaging systems (i.e., Lotus Notes and Microsoft Exchange), gateways to legacy systems such as IBM hosts, and network management systems.

Users interact with applications in front-end systems to make requests on back-end systems. The back-end systems then process the requests, searching and sorting data, serving up files, and providing other services. Back-end systems are physically close to data storage systems, so this arrangement uses the network efficiently.

Three-tier systems extend the client/server system by adding a middle system that performs some processing normally done by either the client or the server. Most important, the middle tier in mission-critical business environments holds the business logic (rules, procedures, and/or operational sequences) that is shared by all applications.

When Internet/intranet technologies are used, a Web server may exist at the middle tier. It accepts requests from clients, screens the requests, passes those requests to back-end systems, accepts the response, formats it into a Web page, and sends the Web page to the user. This system is scalable. If traffic increases, the Web server can distribute some of its workload to peer servers that are not as busy. See &quot;Load Balancing.&quot;

For example, an online registration system built around Microsoft technology may employ Internet Explorer front-end interfaces and a Microsoft SQL Server back-end database. The middle tier consists of a Windows NT/Windows 2000 server running Microsoft Internet Information Server (IIS) that uses ActiveX technology and Active Server Pages (ASPs). When users access the Web server, the ActiveX components are downloaded to the client to provide client-side support for accessing the back-end database information.

Cheers
Brandon J. Deboer

Backend Computer Systems

&lt;a href=&quot;http://www.backendcomputersys.com&quot; rel=&quot;nofollow&quot;&gt;</description>
		<content:encoded><![CDATA[<p>&#8220;Back-end systems&#8221; loosely refers to servers, superservers, clustered systems, midrange systems, and mainframes that provide data services to users. The location of these services is often called the server farm or data center.</p>
<p>The server in client/server refers to the back-end systems. Client/server computing splits processing between a front-end application that runs on the client&#8217;s workstation, and back-end services. Typical back-end services include database management systems (DBMSs), messaging systems (i.e., Lotus Notes and Microsoft Exchange), gateways to legacy systems such as IBM hosts, and network management systems.</p>
<p>Users interact with applications in front-end systems to make requests on back-end systems. The back-end systems then process the requests, searching and sorting data, serving up files, and providing other services. Back-end systems are physically close to data storage systems, so this arrangement uses the network efficiently.</p>
<p>Three-tier systems extend the client/server system by adding a middle system that performs some processing normally done by either the client or the server. Most important, the middle tier in mission-critical business environments holds the business logic (rules, procedures, and/or operational sequences) that is shared by all applications.</p>
<p>When Internet/intranet technologies are used, a Web server may exist at the middle tier. It accepts requests from clients, screens the requests, passes those requests to back-end systems, accepts the response, formats it into a Web page, and sends the Web page to the user. This system is scalable. If traffic increases, the Web server can distribute some of its workload to peer servers that are not as busy. See &#8220;Load Balancing.&#8221;</p>
<p>For example, an online registration system built around Microsoft technology may employ Internet Explorer front-end interfaces and a Microsoft SQL Server back-end database. The middle tier consists of a Windows NT/Windows 2000 server running Microsoft Internet Information Server (IIS) that uses ActiveX technology and Active Server Pages (ASPs). When users access the Web server, the ActiveX components are downloaded to the client to provide client-side support for accessing the back-end database information.</p>
<p>Cheers<br />
Brandon J. Deboer</p>
<p>Backend Computer Systems</p>
<p><a href="http://www.backendcomputersys.com"></a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

