Feb 24

Choosing Web Site Providers and Approaches

A few thoughts for those about to have a Web site built for their business.

Some thoughts for acquirers of Web Sites to help understand the choices that they are presented with.

Mostly they go to a Web agency of some sort then go along with what they say. They pick the agency based on prior work, which may or may not really be analogous to their specific needs. Usually the choice is made on what prior web sites look like, so a high premium is placed on design, often over functionality.

Some Web providers make, shall we say, interesting claims, when it come to Search Engine Optimization (SEO). This a rather large topic that won't be covered here, but be very wary of exaggerated claims. Google is pretty smart in this area and there are increasing stories of sites and companies loosing SEO rankings due to bad practices.

Some considerations for choosing Web hosting tools and suppliers follows.

It is interesting how little most people understand about Web sites. Most Web sites are accomplished using some sort of Web Framework, such as Wordpress or ASP.NET MVC, Microsoft technologies. Some of the other top frameworks are Drupal (used by WhiteHouse.gov), Joomla (examples), Ruby on Rails (examples) and my personal favorite Django (used by National Geographic, PBS, and NASA, others ). There are literally hundreds if not thousands of such frameworks each with its own strengths and weaknesses.  The framework often determines what the Web provider can do in a timely and cost effective manner and how much the end user can do for themselves. There is no one size fits all solution.

Beyond flexibility and efficiency, security is another aspect of Web Frameworks. It is not simply a matter of getting the firewall right. With some notable exceptions, firewall configuration is now pretty well understood, Only open port 80. But sadly that does not provide much security for many of the most common web attack vectors. Specifically it provides no protection for  Cross-Site Request Forgery (CSRF) errors nor XSS issues explored here XSS Prevention Cheatsheet nor does it provide much for mis-configured servers and databases, the most common security issues for Wordpress (details on Wordpress security advice is here), and other frameworks. In fact this list of attacks http://www.owasp.org/index.php/Category:Attack contains none that are inhibited by firewall configuration.

Most any Web framework provides a fairly large exposed surface from a security standpoint.

Another consideration is where the site will be hosted. Many agencies do try to get the hosting business at the same time as the development business. Sometimes there is an urge to host the site on some sort of internal capacity. In general one would be much better of having the site hosted by  a real Web host rather than a small service provider for security, scalability and reliability, not to mention that most large Web hosts have inherent disaster backup that local companies would have a hard time replicating. Security threats such as denial of service (DOS) attacks are best handled by the larger providers.

There is however an emerging class of frameworks that is pretty bullet-proof, known as static sites. That does not mean that the sites do not have controlled levels of interaction or animation, but rather that the site and framework has no executing code on the server, it is in a very real sense entirely pre-compiled. Many smaller company sites are very amenable to this approach.

A leading implementation is Blogofile. Interestingly this was just recently implemented on Google App-engine, (Details here) It can also run on a free micro site instance at Amazon EC2  and or EC3 for very little. So for medium sized traffic the hosting can be free or nearly so. Of course these static sites are easy to host on internal infrastructure as well. Static sites do not however provide for user input, other than basic site search or commenting, usually provided by a third party service such as  DISQUS.

A Major advantage other that security is that since the sites are static HTML with the possible incorporation of Javascript, they are very fast and impose minimal load on the server. The dynamic aspect of web sites that are enabled by the frameworks in many cases is not needed. If there's any need for dynamic features, they can be provided at a per-path level or provided on subdomains, so that they aren't going out of their way to use a framework for portions that static files suffice for.

Static sites are maintained off line, behind the firewall and once updated the entire site, or just the "diff" (an automatically calculated change set) is pushed to the server for new articles and content, most ideally from a change control system such as GIT or Mercurial. This provides excellent change tracking, control and distributed contribution and multiple author capability.

It is further, easy to incorporate differing media types and embed links such as pictures video files and PDF's.

Do yourself a favor and before you invest or get invested in a full framework give static sites a look. Further, if your needs are more modest things like Google sites and other hosted full solutions like Squarespace can be quite satisfactory.

Tags: providers, service, Web


OSWCO is dedicated to introducing and supporting Open Source Software to the Enterprise. The Open Source movement and products have become highly sophisticated, cost effective, and mature. Many leading companies and organizations are making rapidly increasing investments in it's use.

To see our Information about Google Apps click Google Apps Info

OSWCO is an authorized Google Apps reseller. Some organizations need help and a place to turn to for, consulting, product development or commercial support. We have developed an extensive network of reliable experts to assist you, able to take on the largest turnkey projects. Contact us to help you examine the options. Phone: 205-267-1089. More info:

Subscribe to us:



Recent Posts



Popular Posts

Django Popular