Physcial three-tier survey
-
Pay attention, please, as it would be easy to just give an answer without fully reading the question: "For those of you that have built a system that utilizes three physical layers (for the sake of argument UI-Presentation, Business Middle-Tier, and Back-end or DB) how many have actually scaled the system out beyond: n-1-1? (read: n UI servers, 1 middle-tier, 1 DB) Have you successfully deployed an n-n-1 or an n-n-n? If you call your application an n-tier application could you physically deploy it n-1-1? (many can't and deployment is actually n-1 or logical layers)" A curious mind wants to know.
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. I also do Android Programming as I find it a refreshing break from the MS. "And they, since they Were not the one dead, turned to their affairs" -- Robert Frost
-
Pay attention, please, as it would be easy to just give an answer without fully reading the question: "For those of you that have built a system that utilizes three physical layers (for the sake of argument UI-Presentation, Business Middle-Tier, and Back-end or DB) how many have actually scaled the system out beyond: n-1-1? (read: n UI servers, 1 middle-tier, 1 DB) Have you successfully deployed an n-n-1 or an n-n-n? If you call your application an n-tier application could you physically deploy it n-1-1? (many can't and deployment is actually n-1 or logical layers)" A curious mind wants to know.
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. I also do Android Programming as I find it a refreshing break from the MS. "And they, since they Were not the one dead, turned to their affairs" -- Robert Frost
We have deployed several n-n-n websites and applications, using some quite clever (even if I do say so myself) fall through behaviour to cope with load and server balancing.
I have CDO, it's OCD with the letters in the right order; just as they ruddy well should be
-
Pay attention, please, as it would be easy to just give an answer without fully reading the question: "For those of you that have built a system that utilizes three physical layers (for the sake of argument UI-Presentation, Business Middle-Tier, and Back-end or DB) how many have actually scaled the system out beyond: n-1-1? (read: n UI servers, 1 middle-tier, 1 DB) Have you successfully deployed an n-n-1 or an n-n-n? If you call your application an n-tier application could you physically deploy it n-1-1? (many can't and deployment is actually n-1 or logical layers)" A curious mind wants to know.
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. I also do Android Programming as I find it a refreshing break from the MS. "And they, since they Were not the one dead, turned to their affairs" -- Robert Frost
I ran a system that was n-3-3 for a while a few years ago. We had a shared database that was replicated across 3 sites. Each site had a com+ server that pointed to a DB (normally the one on the LAN but could be changed via the registry to point elsewhere). Clients were configured to use the local com+ server. The system worked pretty well when we had DB server problems but the increased number of servers in the chain inevitably led to a slight increase in totally number of outages (even if those could be worked around really quickly)
-
Pay attention, please, as it would be easy to just give an answer without fully reading the question: "For those of you that have built a system that utilizes three physical layers (for the sake of argument UI-Presentation, Business Middle-Tier, and Back-end or DB) how many have actually scaled the system out beyond: n-1-1? (read: n UI servers, 1 middle-tier, 1 DB) Have you successfully deployed an n-n-1 or an n-n-n? If you call your application an n-tier application could you physically deploy it n-1-1? (many can't and deployment is actually n-1 or logical layers)" A curious mind wants to know.
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. I also do Android Programming as I find it a refreshing break from the MS. "And they, since they Were not the one dead, turned to their affairs" -- Robert Frost
I did an n-1-n a long time back. I had n servers, each with a DB, etc. and someone broke in the office over night and stole them, so that was n-n = 0. They also stole a borrowed laptop, so that was n-1-n = -1. In other words, I lost all the servers and owed someone else for their laptop, too. That didn't work worth sh*t.
CQ de W5ALT
Walt Fair, Jr., P. E. Comport Computing Specializing in Technical Engineering Software
-
Pay attention, please, as it would be easy to just give an answer without fully reading the question: "For those of you that have built a system that utilizes three physical layers (for the sake of argument UI-Presentation, Business Middle-Tier, and Back-end or DB) how many have actually scaled the system out beyond: n-1-1? (read: n UI servers, 1 middle-tier, 1 DB) Have you successfully deployed an n-n-1 or an n-n-n? If you call your application an n-tier application could you physically deploy it n-1-1? (many can't and deployment is actually n-1 or logical layers)" A curious mind wants to know.
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. I also do Android Programming as I find it a refreshing break from the MS. "And they, since they Were not the one dead, turned to their affairs" -- Robert Frost
Did 6-6-1 a long time ago. Given that the second to the last app that I worked on handled 4,000 requests/sec on one box, I would avoid attempting to build a multiple physical tier app these days.
I can imagine the sinking feeling one would have after ordering my book, only to find a laughably ridiculous theory with demented logic once the book arrives - Mark McCutcheon
-
Pay attention, please, as it would be easy to just give an answer without fully reading the question: "For those of you that have built a system that utilizes three physical layers (for the sake of argument UI-Presentation, Business Middle-Tier, and Back-end or DB) how many have actually scaled the system out beyond: n-1-1? (read: n UI servers, 1 middle-tier, 1 DB) Have you successfully deployed an n-n-1 or an n-n-n? If you call your application an n-tier application could you physically deploy it n-1-1? (many can't and deployment is actually n-1 or logical layers)" A curious mind wants to know.
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. I also do Android Programming as I find it a refreshing break from the MS. "And they, since they Were not the one dead, turned to their affairs" -- Robert Frost
Only twice did I break the 1-1-1 barrier, thankfully both were a success, though I can assure you the first time I did it, I was quite terrified. Knowing, theoretically, that something has to work in a particular manner, will not abate launch jitters. The first time around at least.
If the post was helpful, please vote, eh! Current activities: Playing Star Craft II. Don't bother me, eh? Now and forever, defiant to the end. What is Multiple Sclerosis[^]?
-
Pay attention, please, as it would be easy to just give an answer without fully reading the question: "For those of you that have built a system that utilizes three physical layers (for the sake of argument UI-Presentation, Business Middle-Tier, and Back-end or DB) how many have actually scaled the system out beyond: n-1-1? (read: n UI servers, 1 middle-tier, 1 DB) Have you successfully deployed an n-n-1 or an n-n-n? If you call your application an n-tier application could you physically deploy it n-1-1? (many can't and deployment is actually n-1 or logical layers)" A curious mind wants to know.
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. I also do Android Programming as I find it a refreshing break from the MS. "And they, since they Were not the one dead, turned to their affairs" -- Robert Frost
Worked at a online poker company that did something close to 20-20-1-3-1 (client servers - proxy servers - game server - logging servers - DB server). There where more servers involved for other features like banking / payments etc, support, etc.
Todd Smith
-
Pay attention, please, as it would be easy to just give an answer without fully reading the question: "For those of you that have built a system that utilizes three physical layers (for the sake of argument UI-Presentation, Business Middle-Tier, and Back-end or DB) how many have actually scaled the system out beyond: n-1-1? (read: n UI servers, 1 middle-tier, 1 DB) Have you successfully deployed an n-n-1 or an n-n-n? If you call your application an n-tier application could you physically deploy it n-1-1? (many can't and deployment is actually n-1 or logical layers)" A curious mind wants to know.
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. I also do Android Programming as I find it a refreshing break from the MS. "And they, since they Were not the one dead, turned to their affairs" -- Robert Frost
Although most end up 1-1-1, its good to have the layers for ogranizational purposes. That being said, I did work on a project for an American Auto Manufacturer that used MS best practices to develop an SOA solution (obviously to be scaled), but the overhead of the chatter between services probably made it less efficient. :laugh: