Hosting

498 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
498
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
11
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Hosting

  1. 1. Hosting Drupal – Getting Started! Mark Schoonover – ThetaJoin mark@thetajoin.com SandCamp 2010
  2. 2. Drupal Requirements ● LAMP stack http://www.thetajoin.com
  3. 3. Drupal Requirements ● LAMP stack ● Linux (Redhat, CentOS, Ubuntu) - OS ● Apache (lighttpd, Nginx) - Webserver ● MySQL (PostgreSQL) - Database ● PHP – Hypertext Preprocessor http://www.thetajoin.com
  4. 4. Drupal Requirements ● LAMP stack This eliminates general webhosting services that only have a webserver running to serve static content – html or javascript files. http://www.thetajoin.com
  5. 5. Shared Hosting ● What is it? http://www.thetajoin.com
  6. 6. Shared Hosting ● What is it? Everything about the server is shared among many websites. Creative Commons Attribution ShareAlike 3.0 http://www.thetajoin.com
  7. 7. Shared Hosting ● What is it? Everything about the server is shared among many websites. ● CPU ● Memory ● Disk I/O ● Disk Space ● Internet Connection http://www.thetajoin.com
  8. 8. Shared Hosting ● How does it work? http://www.thetajoin.com
  9. 9. Shared Hosting ● How does it work? ● Name Based ● IP Based http://www.thetajoin.com
  10. 10. Shared Hosting ● Pros of shared hosting... http://www.thetajoin.com
  11. 11. Shared Hosting ● Pros of shared hosting... ● Low cost ● All system administration handled by hosting company ● Requires less system administration expertise ● All LAMP software installed, ready to go ● Web based control panels ● Easy to get started – relatively ● Plenty of hosting companies to choose from http://www.thetajoin.com
  12. 12. Shared Hosting ● Cons of shared hosting... Part 1 ● Low cost ● All server resources are shared across many websites ● Little to no performance tuning allowed ● Run extra software not needed by Drupal http://www.thetajoin.com
  13. 13. Shared Hosting ● Cons of shared hosting... Part 2 ● Hostname based hosting doesn't support SSL/TLS ● DNS problems will break hostname based hosting ● Security due to misconfigured file permissions ● Shared hosting aims for middle ground to run other CMS ● Can't use different OS, webserver, or database software http://www.thetajoin.com
  14. 14. Shared Hosting http://www.thetajoin.com
  15. 15. Shared Hosting Site backups?? – Don't pull an Atwood! http://www.thetajoin.com
  16. 16. Virtual Private Server Also called ● VPS ● Virtual Dedicated Server (VDS) http://www.thetajoin.com
  17. 17. Virtual Private Server ● What is it? http://www.thetajoin.com
  18. 18. Virtual Private Server ● What is it? ● It's between shared and dedicated hosting ● Can be unmanaged or fully managed http://www.thetajoin.com
  19. 19. Virtual Private Server How does it work? http://www.thetajoin.com
  20. 20. Virtual Private Server ● Pros of VPS... Part 1 ● Choose OS – Redhat, Ubuntu, Debian ● Choose any combination of webserver, database, or PHP to run Drupal ● Virtual hosts can be “resized” on the fly ● Resources can be Fair Shared ● Full root access http://www.thetajoin.com
  21. 21. Virtual Private Server ● Pros of VPS... Part 2 ● Perfomance can be burstable ● Minimum or maximum performance guarantee ● Hardware & O/S managed by hosting company ● No one else on your VPS ● Server cloning http://www.thetajoin.com
  22. 22. Virtual Private Server ● Pros of VPS... Part 3 ● Drupal performance tunable to your exact needs ● Hosting provider may provide entire server snapshots ● Less complexity ● Higher performance than shared hosting http://www.thetajoin.com
  23. 23. Virtual Private Server ● Pros of VPS... Part 4 ● Hosting provider may have Service Level Agreements ● Dedicated IP address allows SSL certificates ● Run multiple Drupal sites on single VPS http://www.thetajoin.com
  24. 24. Virtual Private Server ● Cons of VPS... ● Higher level of technical skills ● Responsible for 100% system administration ● Higher cost ● Server fault & performance typically not managed ● You break it, you fix it! http://www.thetajoin.com
  25. 25. Virtual Private Server http://www.thetajoin.com
  26. 26. Dedicated Server ● What is it? http://www.thetajoin.com
  27. 27. Dedicated Server ● What is it? ● Entire server is YOURS!! – Hosting owned or private owned ● Different kinds – Fully Managed – Totally hands off – Managed – Medium level – Self Managed – Possibly all software, no hardware – Unmanaged – 100% yours to manage http://www.thetajoin.com
  28. 28. Dedicated Server ● Pros of Dedicated Server? ● Ultimate performance – Absolutely no one on your server – You pick datacenter location – You pick all the hardware – Multi-server Drupal http://www.thetajoin.com
  29. 29. Dedicated Server ● Pros of Dedicated Server? ● Ultimate Flexibility – Different server hardware for webserver or database server – Different OS for webserver or database server – Introduce dedicated cacheing layers – Scale up or scale out http://www.thetajoin.com
  30. 30. Dedicated Server ● Cons of Dedicated Server? ● Highest cost – Initial purchase – Depreciation – Upgrades http://www.thetajoin.com
  31. 31. Dedicated Server ● Cons of Dedicated Server? ● Highest cost – Initial purchase – Depreciation – Upgrades ● Highest level of technical skills – Hardware & software http://www.thetajoin.com
  32. 32. Dedicated Server ● Cons of Dedicated Server? ● Highest cost – Initial purchase – Depreciation – Upgrades ● Highest level of technical skills –Hardware & software ● Fault & Performance Management http://www.thetajoin.com
  33. 33. Dedicated Server http://www.thetajoin.com
  34. 34. Content Delivery Networks ● What are they? http://www.thetajoin.com
  35. 35. Content Delivery Networks ● What are they? ● Content Delivery Networks (CDN) are used to move bandwidth intensive files off your Drupal hosting server and put them closer to end user computers. ● Content can be audio, video, photos, software, other documents, or static files. http://www.thetajoin.com
  36. 36. Content Delivery Networks ● Popular CDNs – Akamai – Amazon Cloudfront – Amazon Simple Storage Service (S3) – CacheFly – Many more... http://www.thetajoin.com
  37. 37. Content Delivery Networks ● Why use a CDN? ● Performance – This allows many more concurrent users to access bandwidth intensive files than a single Drupal server can support. – Fantastic for downloading or streaming audio and video files http://www.thetajoin.com
  38. 38. Content Delivery Networks ● Why use a CDN? ● Performance – This allows many more concurrent users to access bandwidth intensive files than a single Drupal server can support. – Fantastic for downloading or streaming audio and video files. ● Mass Storage – Nearly unlimited storage for your files http://www.thetajoin.com
  39. 39. Content Delivery Networks ● When to use a CDN? ● Performance – Large audio/video files make your Drupal server internet connection a bottleneck. – Many smaller files frequently accessed bottleneck your Drupal server internet connection. – Your Drupal server can't stream audio or video successfully. ● Mass Storage – You're running out of storage on your Drupal server. – You don't want to store very large files in your Drupal directory structure. http://www.thetajoin.com
  40. 40. Content Delivery Networks ● Drawbacks using CDNs? ● Added complexity – More things to break – Additional administrative overhead – Drupal can't make using CDNs all automatic – Works for you, but not for others – Dynamic content – Can't be used for database storage – Outside Drupal security http://www.thetajoin.com
  41. 41. “The Cloud” http://www.thetajoin.com
  42. 42. The “Cloud” ● What is that? ● The “Cloud” provides a platform, or infrastructure as a service. ● New application of existing technology ● Instead of many websites on a single host like shared hosting, there are many websites spread across many servers or “clusters”. http://www.thetajoin.com
  43. 43. The “Cloud” ● What are clusters? Clusters are simply multiple webservers, database servers, or PHP servers configured to act as one large, powerful server. http://www.thetajoin.com
  44. 44. The “Cloud” ● What does it mean? ● Infrastructure as a service means you don't have to worry about the hardware or software your Drupal site runs on. ● The infrastructure is built on a large number of web and database servers working together in clusters. http://www.thetajoin.com
  45. 45. The “Cloud” ● How do they work? ● Register for an account ● Transfer your Drupal files ● Transfer Drupal database ● Configure DNS http://www.thetajoin.com
  46. 46. The “Cloud” ● How do they work? ● Register for an account ● Transfer your Drupal files ● Transfer Drupal database ● Configure DNS Same as any other hosting service. http://www.thetajoin.com
  47. 47. The “Cloud” ● Benefits of the Cloud? ● Scalability ● High redundancy ● Utility pricing, pay as you go http://www.thetajoin.com
  48. 48. The “Cloud” ● Cons of the Cloud? ● You have to make sure everything works on the cloud platform. ● No performance tuning ● Latency issues between clusters ● Cloud component upgrades could break Drupal ● May not be cost effective for smallish sites ● Security http://www.thetajoin.com
  49. 49. The “Cloud” http://www.thetajoin.com
  50. 50. Slides of this talk available on: http://www.thetajoin.com - SandCAMP
  51. 51. Thank you for attending my SandCAMP 2010 session. I hope you enjoyed the session as much as I did preparing and presenting. For attendees of my sessions & people who download my slides, I'm offering a free Drupal performance analysis of your site! I have to limit this offer to a single site only, so pick your worst! Just email or call to setup an appointment. Hope you had a great time at SandCAMP 2010! Regards, Mark Schoonover http://www.thetajoin.com - The Drupal Hosting & Performance Company Email: mark@thetajoin.com :: Voice: 619-928-4473 :: Fax: 619-374-3130

×