SEO

I have a potential client that is anticipating rapid growth of a web
site they want me to build. Some quick research tells me that there is
the potential for as many as 50 million users that will access the site
for an hour or two every day. All of those users will be located in the
USA so most of the access will be during the day.. To use the web site
you will have to have an account and log in. At this time I can't
really say how much data will need to be stored about each user.

If this site grows as much as this client thinks, will I need to have
some kind of load sharing system to access the database?

I was reading in the MySQL manual about the NDB Cluster storage engine.
Is this something that would work well in a situation like this? One
thing that was mentioned was the possibility of having servers in
different locations which seems to make the Cluster storage engine not a
good choice.

Can someone here give some insight and suggest other options I could
look into?

--
Chris W
KE5GIX

"Protect your digital freedom and privacy, eliminate DRM,
learn more at http://www.defectivebydesign.org/what_is_drm"

Gift Giving Made Easy
Get the gifts you want &
give the gifts they want
One stop wish list for any gift,
from anywhere, for any occasion!
http://thewishzone.com

On 2/26/07, Chris W <2wsxdr5@cox.net> wrote:

>
> Can someone here give some insight and suggest other options I could
> look into?

you could replicate all the data between web/application servers, and
use the local store as a read-only database, and push all your
updates to a central update 'master' server. You could also play with
multiple-master replication.


>
> --
> Chris W
> KE5GIX
>
> "Protect your digital freedom and privacy, eliminate DRM,
> learn more at http://www.defectivebydesign.org/what_is_drm"
>
> Gift Giving Made Easy
> Get the gifts you want &
> give the gifts they want
> One stop wish list for any gift,
> from anywhere, for any occasion!
> http://thewishzone.com
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=cgmckeever@gmail.com
>
>

Complementing Chris :

<http://www.onlamp.com/lpt/a/6549>Asume that your Application Server is
Tomcat.

BALANCING SERVERS:

You can implement some servers or appliance only for balancing your primary
connections. This servers or appliance you must implement using Hearbeat (
only). For example one of the balancing servers fail.

APPLICATION SEVER

Your x ( quantity) of applications servers receive the connections from
Balancing Servers and distribute across the diferent nodes of MySQL using
LVS. You must implement Hearbeat for each application server too ( just in
case of failure of some app. server).


DATABASE SERVERS

MySQL and multimaster replication, please see below
http://www.onlamp.com/lpt/a/6549


Technology : for OS try to use Linux, for Hearbeat try to use UltraMonkey (
www.ultramonkey.org) for Balancing try to use LVS ( Linux).


I hope this help.

Regards.
Juan Eduardo


On 2/26/07, Chris McKeever <cgmckeever@gmail.com> wrote:
>
> On 2/26/07, Chris W < 2wsxdr5@cox.net> wrote:
>
> >
> > Can someone here give some insight and suggest other options I could
> > look into?
>
> you could replicate all the data between web/application servers, and
> use the local store as a read-only database, and push all your
> updates to a central update 'master' server. You could also play with
> multiple-master replication.
>
>
> >
> > --
> > Chris W
> > KE5GIX
> >
> > "Protect your digital freedom and privacy, eliminate DRM,
> > learn more at http://www.defectivebydesign.org/what_is_drm"
> >
> > Gift Giving Made Easy
> > Get the gifts you want &
> > give the gifts they want
> > One stop wish list for any gift,
> > from anywhere, for any occasion!
> > http://thewishzone.com
> >
> >
> > --
> > MySQL General Mailing List
> > For list archives: http://lists.mysql.com/mysql
> > To unsubscribe: http://lists.mysql.com/mysql?unsub=cgmckeever@gmail.com
> >
> >
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:
> http://lists.mysql.com/mysql?unsub=j...domc@gmail.com
>
>

If you can wait for 5.1 (in beta now), you can use partitioning to store
a client on a different database in a different geographical site. You'd
need to partition by region/state (assuming you capture address info).
If you wanted to do any reporting, however, you'd need to set up a data
warehouse, and every night do an extract-transform-load (ETL) from the
regional "sites" into your main database.

It might make more sense to have "mini-sites" all over the country -
database, web and application servers.

Since it sounds like development hasn't started, you can probably go
with 5.1 - it should be released before summer.

David

Chris W wrote:
> I have a potential client that is anticipating rapid growth of a web
> site they want me to build. Some quick research tells me that there
> is the potential for as many as 50 million users that will access the
> site for an hour or two every day. All of those users will be located
> in the USA so most of the access will be during the day.. To use the
> web site you will have to have an account and log in. At this time I
> can't really say how much data will need to be stored about each user.
> If this site grows as much as this client thinks, will I need to have
> some kind of load sharing system to access the database?
> I was reading in the MySQL manual about the NDB Cluster storage
> engine. Is this something that would work well in a situation like
> this? One thing that was mentioned was the possibility of having
> servers in different locations which seems to make the Cluster storage
> engine not a good choice.
>
> Can someone here give some insight and suggest other options I could
> look into?
>