Are we still separating application roles out on different servers?
-
@dave247 said in Are we still separating application roles out on different servers?:
For example, if I have an application with a web front-end and an SQL database back-end - in the past, it used to be best practice to separate those two roles and have one server for the webserver and another server for the SQL database server.
That was never a best practice. Generally separating is good, but not always, it's a specific evaluation. And the one that you describe is actually where you rarely do it, both today and historically.
-
-
@scottalanmiller said in Are we still separating application roles out on different servers?:
@dave247 said in Are we still separating application roles out on different servers?:
For example, if I have an application with a web front-end and an SQL database back-end - in the past, it used to be best practice to separate those two roles and have one server for the webserver and another server for the SQL database server.
That was never a best practice. Generally separating is good, but not always, it's a specific evaluation. And the one that you describe is actually where you rarely do it, both today and historically.
ok, can you provide some sort of info to support that? Not trying to be combative, I honestly want to evaluate it. I will watch your video next chance I get.
-
@dave247 said in Are we still separating application roles out on different servers?:
@scottalanmiller said in Are we still separating application roles out on different servers?:
@dave247 said in Are we still separating application roles out on different servers?:
For example, if I have an application with a web front-end and an SQL database back-end - in the past, it used to be best practice to separate those two roles and have one server for the webserver and another server for the SQL database server.
That was never a best practice. Generally separating is good, but not always, it's a specific evaluation. And the one that you describe is actually where you rarely do it, both today and historically.
ok, can you provide some sort of info to support that? Not trying to be combative, I honestly want to evaluate it. I will watch your video next chance I get.
The big reason is performance and cost. Keeping the two together tends to cost less (especially if doing cloud) and makes it easy to maintain (one VM to backup and deal with.) Now if you do modern things like pure DevOps, automation of builds, backup only non-static DB data, then separate is often better. But if you are more normal and going to backup using Veeam or something, having a contained VM that has everything in one reliable package is a lot easier to protect and restore.
Local DB (inside the VM) means better performance under normal scaling. Lower latency.
-
@scottalanmiller said in Are we still separating application roles out on different servers?:
@dave247 said in Are we still separating application roles out on different servers?:
@scottalanmiller said in Are we still separating application roles out on different servers?:
@dave247 said in Are we still separating application roles out on different servers?:
For example, if I have an application with a web front-end and an SQL database back-end - in the past, it used to be best practice to separate those two roles and have one server for the webserver and another server for the SQL database server.
That was never a best practice. Generally separating is good, but not always, it's a specific evaluation. And the one that you describe is actually where you rarely do it, both today and historically.
ok, can you provide some sort of info to support that? Not trying to be combative, I honestly want to evaluate it. I will watch your video next chance I get.
The big reason is performance and cost. Keeping the two together tends to cost less (especially if doing cloud) and makes it easy to maintain (one VM to backup and deal with.) Now if you do modern things like pure DevOps, automation of builds, backup only non-static DB data, then separate is often better. But if you are more normal and going to backup using Veeam or something, having a contained VM that has everything in one reliable package is a lot easier to protect and restore.
Local DB (inside the VM) means better performance under normal scaling. Lower latency.
Good points Scott, thanks
-
@scottalanmiller said in Are we still separating application roles out on different servers?:
Wow you made a video for/because of me! Nice!
And yeah, I see your points. That all makes sense. I guess I shouldn't have used to words "best practice". I just meant like, the thing that a lot of people commonly do because it's the current trend or whatever.. but yeah its good to question everything and use your brain. I just wanted good input/insight, which I got.
-
@dave247 that's how I roll.
-
@dave247 oh, had you thought that that was me linking a previously made video? Nope, just for this thread
-
@scottalanmiller said in Are we still separating application roles out on different servers?:
@dave247 that's how I roll.
Thanks Scott. You the MVP!
-
@scottalanmiller said in Are we still separating application roles out on different servers?:
@dave247 oh, had you thought that that was me linking a previously made video? Nope, just for this thread
Yeah, just because you've linked your videos in the past where appropriate.
-
@dave247 said in Are we still separating application roles out on different servers?:
@scottalanmiller said in Are we still separating application roles out on different servers?:
@dave247 oh, had you thought that that was me linking a previously made video? Nope, just for this thread
Yeah, just because you've linked your videos in the past where appropriate.
I like to keep people on their toes.
