Written by: host 10/4/2007 12:00 AM
I rarely have an original thought (if I have ever had one) and this entry is no exception. A while back while comparing the Commerce Starter Kit with the DNN Core Store Module, I found an interesting post on “Spooks Blog” (link) discussing the merrits of a DotNetNuke ecommerce module. In response to this post, Sean Walker posted a very eloquent response, in which I found the following especially pointed and relevant to DotNetNuke's use in a great whole: “In response to Rob's comment that DNN is not suited for e-commerce, I would obviously have to disagree. The fact is that anyone who needs to sell goods online also needs a whole array of other services on their website. They will want to customize the look of the website to match their business branding. They may want to provide forums for online support of their products. They may want a Newsletter to push information to their customers. They may need to designate private and public areas of their website for inside/outside sales or marketing information. They will need basic pages which describe the company and their mission. DotNetNuke handles all of these requirements and much more. And I am sure an e-commerce application could eventually provide all of these services, but in my opinion it is then losing its main focus - commerce.” He also addressed performance issues, always a sticky subject with old school manager types: “In terms of performance and scalability, I definitely need to address the facts. DotNetNuke.com is running on a single dedicated web server connected to a database server ( so 2 boxes - no web farm or load balancer ). It is running the DotNetNuke framework with all of the standard defaults for the environment and application - so no custom tweaks or "squeezing" whatsoever ( we purposely avoid custom tweaks so that we stay in touch with our user community ). In January 2006, the site had 4.5 million page views ( or about 150,000 per day ). Obviously, this could scale much higher if we moved to a web farm model ( ie. I have heard of DNN sites handling 1.0M+ page views per day ). February 16, 2006 3:12 AM” I couldn't have put it any better.
I rarely have an original thought (if I have ever had one) and this entry is no exception. A while back while comparing the Commerce Starter Kit with the DNN Core Store Module, I found an interesting post on “Spooks Blog” (link) discussing the merrits of a DotNetNuke ecommerce module.
In response to this post, Sean Walker posted a very eloquent response, in which I found the following especially pointed and relevant to DotNetNuke's use in a great whole:
“In response to Rob's comment that DNN is not suited for e-commerce, I would obviously have to disagree. The fact is that anyone who needs to sell goods online also needs a whole array of other services on their website. They will want to customize the look of the website to match their business branding. They may want to provide forums for online support of their products. They may want a Newsletter to push information to their customers. They may need to designate private and public areas of their website for inside/outside sales or marketing information. They will need basic pages which describe the company and their mission. DotNetNuke handles all of these requirements and much more. And I am sure an e-commerce application could eventually provide all of these services, but in my opinion it is then losing its main focus - commerce.”
He also addressed performance issues, always a sticky subject with old school manager types:
“In terms of performance and scalability, I definitely need to address the facts. DotNetNuke.com is running on a single dedicated web server connected to a database server ( so 2 boxes - no web farm or load balancer ). It is running the DotNetNuke framework with all of the standard defaults for the environment and application - so no custom tweaks or "squeezing" whatsoever ( we purposely avoid custom tweaks so that we stay in touch with our user community ). In January 2006, the site had 4.5 million page views ( or about 150,000 per day ). Obviously, this could scale much higher if we moved to a web farm model ( ie. I have heard of DNN sites handling 1.0M+ page views per day ). February 16, 2006 3:12 AM”
“In terms of performance and scalability, I definitely need to address the facts. DotNetNuke.com is running on a single dedicated web server connected to a database server ( so 2 boxes - no web farm or load balancer ). It is running the DotNetNuke framework with all of the standard defaults for the environment and application - so no custom tweaks or "squeezing" whatsoever ( we purposely avoid custom tweaks so that we stay in touch with our user community ). In January 2006, the site had 4.5 million page views ( or about 150,000 per day ). Obviously, this could scale much higher if we moved to a web farm model ( ie. I have heard of DNN sites handling 1.0M+ page views per day ).
0 comments so far...