| Author |
Message |
mattc58
Joined: 21 Jan 2012
Posts: 1
|
| Posted: Sat Jan 21, 2012 7:13 am Post subject: Should I separate the web and database servers on Linode? |
|
|
Howdy Friends,
I'm working on an application using Django (Python), Apache, and MySQL. Right now everything is on one server, but we're about to go live so I'm looking at infrastructure.
Question: am I better off doing separating the web and database functions into two separate 1024MB servers, or should I use one 2048MB server for the app?
I'd usually vote for separating them, but I'm concerned about doubling my failure points since a failure in either the app or the db causes a system failure. Then again, my previous experience with Linode is that things don't go down. :) |
|
| Back to top |
|
empoweringmedia
Joined: 16 Nov 2011
Posts: 35
Location: United States
|
| Posted: Sat Jan 21, 2012 10:18 am Post subject: |
|
|
Answer is... it depends. It depends upon the amount of traffic you are currently getting and expected growth.
Also it depends upon what you are bound by. Are you bound by CPU? If so then multiple instances would help since by default Linode gives you access to 4 CPUs. Getting one instance would only give you access to 4 CPUs while two instances would give you access to 4 on each.
Though do make sure the instances are on multiple hosts. For reliability (not all eggs in one basket) and for CPU performance. |
|
| Back to top |
|
hoopycat
Joined: 30 Aug 2008
Posts: 1294
Location: Rochester, New York
|
| Posted: Sat Jan 21, 2012 1:14 pm Post subject: |
|
|
Whenever possible, I plan for separate web and database servers. That makes scaling (or redundacation of) either pretty easy. If things get busy, it's probably not the time you'd want to have to deal with factoring out your database so you can have two web servers.
Good news is that Django supports multiple database servers (hooray!), so you can add read-only slaves relatively easily, too. |
|
| Back to top |
|
Mr Nod
Joined: 17 Mar 2009
Posts: 100
Location: UK
|
| Posted: Sat Jan 21, 2012 1:51 pm Post subject: |
|
|
I believe that the django book suggests that you separate out onto different nodes for scalability, i.e. 1 node for webserver, another for db server, another node for static files and so on...
I'd go that way. |
|
| Back to top |
|
Guspaz
Joined: 26 May 2009
Posts: 1150
Location: Montreal, QC
|
| Posted: Mon Jan 23, 2012 11:32 am Post subject: |
|
|
| Linode services don't tend to go down, no, but it has been known to happen. Even the best companies have the occasional downtime when they take an arrow to the knee. |
|
| Back to top |
|
Mr Nod
Joined: 17 Mar 2009
Posts: 100
Location: UK
|
| Posted: Mon Jan 23, 2012 11:49 am Post subject: |
|
|
Guspaz wrote: Linode services don't tend to go down, no, but it has been known to happen. Even the best companies have the occasional downtime when they take an arrow to the knee.
I used to be an adventurer like you... |
|
| Back to top |
|
Azathoth
Joined: 07 Dec 2009
Posts: 263
|
| Posted: Mon Jan 23, 2012 2:36 pm Post subject: |
|
|
| http://youtu.be/mSDfxde8fSg (nsfw) |
|
| Back to top |
|
| |
