My Research on Up-Scaling High Traffic Websites

Note: My most up-to-date (but raw) research will be in this ScalabilityResearch.TXT text file on my local computer.  It can be accessed directly online because of a sweet tool I like to use: GetDropBox

HowTo & Conclusion

After much deliberation I decided to go with the company RackSpaceCloud for hosting our dedicated servers.  Loadbalancing on their servers is DIY (do-it-yourself) which is good because then I have full control over the configuration which will make it easier to scale even more.  The main advantage of using their system is I can duplicate out the webservers easily.  I can create and mirror out full copies of any of our servers in not much more time than what it takes to perform the copy over their intranet.  The price is great too :-)  I can increase the server count at demand and I can scale up servers when needed as well.

Here is a HowTo that I am working on to help those who are interested in setting up a Loadbalanced Apache Server Cluster on Linux/CentOS 5.3.  I will provide more conclusions and howto's here when my research and implementation is complete.

Research Notes

Scalability Research
j0zf 2009.7.5

// GOALS ///////////////////////////////////////////////////////////////////////

1. Scalability
2. Redundency
3. Fail-Over
4. PCI Compliance
 - check list :

// OPTIONS ///////////////////////////////////////////////////////////////////// 

> Cloud Servers
 > RackSpace Cloud
  - may request separate geographic locations for servers.
  - very liberal policy, it just has to be legal.
  - Load balancing is DIY
  - Additional Public IP addresses are $2 / month. (request from support)
 > Amazon EC2
  - may have policy limiting direct marketing, and content.
 > SoftLayer
  - Does Load-balancing (no real clear)
  - More expensive than Rackspace (on average)
 > Google App Engine -
  - ""Lavin" (12:34:44 PM): but that we would have to rewrite our entire system into python"

> In House Servers
 - Possibly using load balancing hardware
  - direct access to servers and hardware.
  - cost of bandwidth
  - up-front cost of servers 
> Rented Servers (Hostgator, etc)
 > Multiple Dedicated Servers
  - x number of webservers using rsync
  - use round-robin dns method
  - dedicated database server
 > Hosting service which provides Load Balanced Servers

> Load Balancing
 > Apache HTTP Server (mod_proxy_balancer)
  - howto: 
 > DNS Load Balancing Options
  * Round robin DNS
  - DnsMadeEasy Round-Robin Load Balancing
  - ?? Can we do this same thing, in-house?
  * Apache Load Balancing 
  - mod_proxy_balancer extension
  - apache2-mpm-worker is pretty fast and light if well-configured.  
  * Pound
  * NginX
  * For Failover
  - heartbeat or something similar would do the failover  

> Database Scaling
 - Phase 1 : Powerful Single-Purpose MySQL Database Server.
 - Phase 2 : Mysql Cluster

// POTENTIAL OBSTACLES /////////////////////////////////////////////////////////

- Multiple wildcard SSL certs on the same server.
 - josephl_ Hydra wants to use their own wildcard SSL certificate rather than the one
// RESEARCH SOURCES ////////////////////////////////////////////////////////////
josephl: <--- this is a neat little guide I found that gives a general introduction
Byron: (HOWTO - Configure Load Balancing)

// CLIENTS /////////////////////////////////////////////////////////////////////

> B
 - Has now:
  - 1 server.
  - backing up to 2nd server.
  - dns fail setup. via dns made easy.
 - Needs:
  - pci compliance, separate server.
  - need a pci server.
  - 5 or 10 crm carts on each server.
  - 1 server, all landing pages, needs to be fast.
  - 1 server, backend crm server, needs to be stable.
  - cluster situation, they host their front end landing pages.
> H
 - Their own wildcard SSL certificate rather than the one.

Joseph Frazier | Create Your Badge

This page has been visited 5,256 times since July 10th, 2009

This is an ApogeeInvent Dynamic Website