Shared Hosting

In shared hosting, your website is virtualized together with other websites on one machine. This means that your website shares resources with other websites. These resources are the CPU, memory and bandwidth allocated to the physical server.

High Performance

Not every site must have a high performance. If you don't plan on selling products through your website, chances are that almost any of the hosting plans out there will suffice. What type of performance can you expect to get from the hosting? What can affect this performance?

Co-hosted websites compete with each other for the hosting server's resources, and that affects your site's performance. This comes down to a very simple queue issue - all the requests that online users make of your website are entered into a queue which holds all the requests that online users make of all the websites sharing the physical server. If one or more of the other websites co-hosted with you has a lot of traffic, or has traffic peaks that interlace with requests your users make - your website will suffer. Response time will be bad, and your users may give up on you.
This does not have to be the case, as some hosting providers have better control over websites performance and will ensure that your website has an equal share of the resources when the server is loaded. However, most hosting services do not offer that except in VPS plans. Another issue to consider is up-time. On shared hosting, there is a bigger chance of the server crashing because a bad script caused it to exahust its resources. This script can stem from your website as well as from another, but the more websites there are on the server - the more likely this is to happen. Good hosting services will have good monitoring and prevention mechanisms, but be aware that not all providers have these.

Private IP Address

Will your website have its own IP address?

As a rule with shared hosting, all the websites co-hosted on the same physical machine share the same IP address. This is a concern since this puts your website in danger of being co-hosted with unethical websites. Unethical websites may be used for spamming or spreading of malicious software. When such a site is found it is usually blacklisted, meaning that servers all over the Internet refuse to accept traffic (such as email) from this site, and search engines no longer list it. This is really bad for your website, because what gets blocked (blacklisted) is the actual IP Address - the same IP Address that you share with such unethical websites. As a result - your website will get blacklisted, even though it didn't do anything wrong. Note that for some hosting providers this is a non-issue, as some hosting services have extremely good mechanisms to find such malicious websites and remove them from the Internet before they get a chance to become blacklisted. This way, the hosting provider protects your site against being blacklisted because other websites misbehaved. Another reason you need to consider a dedicated IP address is for when you want your website to offer SSL communication to users. This can only be performed in a trusted way when your website has its own, dedicated IP. However, this does not always mean you need to get dedicated hosting. With most hosting services you can get a dedicated IP (usually for an extra payment) even though your website is on shared hosting.

Low Cost

How expensive is each of the options?

Shared hosting options, including VPS, are very cheap. Easily a tenth of the cost of the cheapest dedicated servers and less than that.

Server Control

How much control do you have over the server?

With shared hosting, you control your website, as you can upload almost any files you want there. However, you do not control the operating system. You also don't control additional software or the server's hardware. You don't get root access, your own creation of VPS (Virtual Provate Servers), or anything else really. This is not always a bad thing. Sometimes the restricted level of control is better, especially with smaller, low-traffic websites, and if you don't have any knowledge or inclination towards managing your website yourself.

Big Websites Fit

Does this hosting option fit a big website, with a large volume of traffic?

With big, traffic intensive sites, you may really feel the limitations of shared hosting. Performance issues will arise, as other websites compete with you for the same set of resources, and the overall user experience will deteriorate.
On the other hand, when you host a large site on shared hosting, you can concentrate on creating the content for your site, and not worrying about security, patching and other administrative tasks.

Small Websites Fit

Does this hosting option fit a small, low-to-average traffic website with no special needs (e.g. a blog).

Shared hosting is really the way to go for smaller sites. When you are only starting out, or when you feel your website is small and will not have substantial traffic or serve large amounts of multimedia content.

High Security

What are the security implications of going this way or the other?

With the shared hosting option, the hosting provider is responsible for patching the server operating system, and employing the system-related security practices. This makes your life very easy, especially if you only have a small website and don't want to deal with all the technical issues around the servers yourself. On the other hand, with shared hosting, the external security mechanisms (e.g. firewalls) employed by the hosting provider can not always be tailored specifically to your website's needs.

Click on any product below to compare it to the Shared Hosting.

Or search for similar products:

Related comparisons

There are no product images available.

Average rating: 5 / 5 , based on 41 customer reviews
Feel factor: 5


good but out dated

(score 3/5)

This book is a very good introduction to Drupal. The source code and specific instructions are out dated. e.g., In chapter 4, the Amazon module configuration instruction does not work and the source codes' profiles are full of error after installation. The authors need to publish the latest updated materials on the book's website. The book deserves a 5 star rating if not for these short comings. If you are new to Drupal, these errors will make following the book very difficult.

Posted on: 2010-09-09
By Vincent Wong



Well structured, just like Drupal.

(score 5/5)

Drupal is a fast-moving target, so writing a book about it is especially challenging. These authors know what they are doing, as they are all long time Drupal jockeys, deeply involved with core development, the Drupal community, and with Drupal education. With six different authors, it's refreshing that they have been able to combine their points of view into such a well-integrated publication.

Content structure is what Drupal is all about, and the authors have also structured their book's content to make it easily accessible. After the first chapter, each is presented with the same sectional structure, beginning with a case study, a common real-world problem that Drupal might be asked to solve. This structure next leads to alternative implementation strategies, then focuses on the features of recommended modules. In their "Hands-on" section, the authors next show how to configure the modules. The chapters, each on a different case study, end with references to other modules that might further enhance functionality. Each chapter ends with a summation, including links to the modules discussed. In the course of describing solutions to the problems introduced by the case studies, the authors take the reader (with little redundancy) through many general aspects of planning and implementing a Drupal site.

The authors' choice of case studies makes the book particularly valuable, as they cover a range of very common content management situations, including: a job posting board, product reviews, a wiki, managing publishing workflow, a photo gallery, multilingual sites, event management, and an online store.

Site functionality is the focus of most of the book, but the last chapter addresses more the topic of presentation, in Drupal-speak, Theming. This chapter requires some knowledge of CSS, HTML and PHP to fully understand how to modify existing themes (of which there are many). There is reference to where you can learn more about these topics, as well as some code that you can copy, but the authors do not attempt to write a primer on web coding.

Before the index, the book ends with three Appendices. The first addresses Drupal installation and maintenance. The second gives advice on choosing and evaluating modules that you might want to use for your own purpose. Since many modules are contributed by users in the Drupal community, coding quality, bug fixes, etc. can vary considerably, and the user is well-advised to apply "due diligence" as introduced in this appendix. The third appendix is a list of modules and themes used in the book, along with where to get them and their source code.

Using Drupal is targeted at readers "somewhere between total newbie and computer science professor", and is a surprisingly accessible practical introduction to Drupal as a platform. The writing style is succinct but easy to read, without the cutesy fluff so often found in how-to technical writing for the masses. The presentation reflects the authors' continuing involvement in Drupal education and in the growing Drupal community.

Posted on: 2010-05-11
By lightscapes
Helpful index: 100%



Best beginner book out there

(score 5/5)

This is the best book for beginners new to Drupal. You can follow along and build a site, learning what you need to know along the way. This is a much more fun and rewarding way to learn, and people seem to understand more quickly and retain the information longer because they're actually using it. At our university, this is the book we recommend to people who are just starting out with Drupal and have a little experience with the web (i.e., some CSS and HTML). No PHP required.

Posted on: 2010-05-02
By Kathy
Helpful index: 100%



Less Than Expected

(score 1/5)

I always expect O'Reilly books to lead me into new areas. I have been using them as a source for years. This is the first time I have been disappointed. The author is hard to read. The examples used inside the FIGURES boxes have been reduced in size to the point where they are almost impossible to read(use). I got a basic idea about DRUPAL but gave up after 130 pages. Then I ordered another book from someone else.

Posted on: 2010-03-22
By Richard D. Vogel
Helpful index: 0%



The best choice for a single Drupal book!

(score 5/5)

As a Drupal newbie, I found this book the ideal starting point for the somewhat daunting task of learning Drupal. Its hands-on sections walk you step-by-step through the process of creating websites that serve real needs, and take you from the earliest steps (what is this thing called Drupal? How do I get it to do something?) through a wide range of tasks, from creating a photo gallery to an online store.

During the course of this journey, you will learn both Drupal core and a wide variety of contributed modules. The writing and the instructions are easy to follow, neither too technical nor condescending. The sample projects are real enough to give a genuine sense of how to use the tools without being so verbose as to bog you down in details.

I have read other Drupal books, but so far none takes the place of this one as a real-world text in getting the most out of a wonderful tool.



Posted on: 2010-03-08
By Lawrence Baldwin
Helpful index: 100%

Use the sliders to set your priorities, and find what's best for you in  Website Hosting Types



2
High Performance
2
Private IP Address
2
Low Cost
2
Server Control
2
Big Websites Fit
2
Small Websites Fit
2
High Security
Latest products Departments Hot products
User:
Password: