http://www.jamesguest.co.uk Digital consultant & project manager Tue, 12 Jul 2011 14:20:30 +0000 hourly 1 http://www.jamesguest.co.uk/latest/2011/06/ten-steps-to-protect-against-vulnerability/#comment-5 James Guest Tue, 12 Jul 2011 14:20:30 +0000 http://blog.jamesguest.co.uk/?p=128#comment-5 Thanks Jamie. I totally understand and agree that specific hosting requirements can sometimes be necessary and costly for complex or custom builds. However, this in itself is a potential risk. I would normally factor in the hosting requirements when selecting a technology to use. Expensive, non-standard requirements may be a good reason to opt for an alternative technology. I also agree that set-up, maintenance and ongoing support costs are a factor. These should always be considered at that outset of a project, as they should be in addition to the hosting costs regardless of who owns the server. Thanks Jamie. I totally understand and agree that specific hosting requirements can sometimes be necessary and costly for complex or custom builds. However, this in itself is a potential risk. I would normally factor in the hosting requirements when selecting a technology to use. Expensive, non-standard requirements may be a good reason to opt for an alternative technology. I also agree that set-up, maintenance and ongoing support costs are a factor. These should always be considered at that outset of a project, as they should be in addition to the hosting costs regardless of who owns the server.

]]> http://www.jamesguest.co.uk/latest/2011/06/ten-steps-to-protect-against-vulnerability/#comment-4 Jamie Saunders Tue, 12 Jul 2011 12:47:51 +0000 http://blog.jamesguest.co.uk/?p=128#comment-4 Thanks for a great article James, you make a lot of valid points. Although I do understand why you advise to keep hosting in the client's own name, there are situations in which this is not practical. For instance, when a client requires the power of a dedicated server but cannot afford the outlay of renting an entire dedicated server themselves, espcailly with when very specific hosting environments are needed – this can be very expensive when you take into account set-up, maintenance and ongoing rental costs, often reaching hundreds of pounds or more per month. However, if backups are taken regularly and the domains decoupled from the hosting, if the worse came to the worse the client could recover by 'swapping out' the hosting service, setting up their site elsewhere and repointing the domain. Thanks for a great article James, you make a lot of valid points. Although I do understand why you advise to keep hosting in the client’s own name, there are situations in which this is not practical. For instance, when a client requires the power of a dedicated server but cannot afford the outlay of renting an entire dedicated server themselves, espcailly with when very specific hosting environments are needed – this can be very expensive when you take into account set-up, maintenance and ongoing rental costs, often reaching hundreds of pounds or more per month. However, if backups are taken regularly and the domains decoupled from the hosting, if the worse came to the worse the client could recover by ‘swapping out’ the hosting service, setting up their site elsewhere and repointing the domain.

]]>