Soft Skills: Scaling out vs scaling up

Scaling UP vs Scaling OUT Scaling up refers to becoming a more effective person by increasing your personal efficiency. Scaling out refers to being a more effective person by engaging others to help solve your problems.    While scaling out is initially more difficult than scaling up, it has the potential for significantly more effectiveness than scaling up, so you should spend time investing in both types of scaling.

To understand the entomology of these terms lets look at the computer domain.  In the domain of computers there are two common ways to achieve more computing power or scale. Scaling up and scaling out.

Scaling up refers to getting more computing hardware for a single machine.  For example,  getting more RAM, faster CPUs or even bigger disks for the same computer.     On the other hand, scaling out refers to getting more computers. Instead of making your single computer faster you break up the problem so it can be processed by multiple computers and use the multiple computers to get the job done.

Scaling out requires changing the way the problem is solved, forcing co-ordination and making the problem more complex. As a result scaling up sounds like the way to scale.

At first, scaling up is  the easy way to scale. You throw some new hardware in the computer, and without much work you have more computing power.   As you upgrade your computer you start getting diminishing returns. Consecutive upgrades get more and more expensive, until eventually you can no longer upgrade your computer as it will be at its maximum power.  At this point you have no choice but to scale out.

Scaling out is hard. It requires you to think about how the problem can be broken up, how the computers can be coordinated and  how to keep the computers synchronized.  However, once you've made your problem solvable through scale-out solutions you can often add lots of computers. By scaling out, you can have significantly more computing power then you could ever have via a scale up solution.

As with computers and computing power, people often require more effectiveness to solve their problems. They have two ways to solve their problems, either they scale up, by becoming more efficient, or they scale out by engaging others to help solve their problems.

Humans scaling up reach diminishing returns - an easy to understand limit is the hours in a day.  Regardless of how efficient you are, you still only get 24 hours in a day.

As an alternative to scaling up, humans can scale out.  Scaling out requires figuring out how to break up problems so more than one person can work on them, and figuring out how the people will co-ordinate.

While scaling out is initially more difficult than scaling up, it has the potential for significantly more effectiveness than scaling up, so you should spend time investing in both types of scaling.

If you've read the 7 habits of highly effective people, you may notice that scaling up refers to the 3 habits of independence, while scaling out refers to 3 habits of interdependence.  I'll spend many more posts discussing these two types of scaling.

Comments

ReaderThinker said…
A nice way of thinking about these concepts, thanks for posting.
11/19/2014 9:30 AM
Post a Comment

Popular posts from this blog

Finding CLR exceptions without visual studio

(If you want to understand what exception code 0xe0434352 is, read this post ) Often exceptions are thrown and caught and you don't see them. You probably know how to debug this in Visual Studio, so let me show you how to do it in cdb. Sample Code: class Program { static void Main(string[] args) { foreach (var x in Enumerable.Range(0,2000)) { Thread.Sleep(TimeSpan.FromSeconds(1)); Console.WriteLine("Hello World"); ThrowAndCatchException(); } } private static void ThrowAndCatchException() { try { throw new NotImplementedException(); } catch(Exception) { } } } Output of the application: Hello World Hello World Hello World Nothing about an exception, but you're sure it's happening behind the covers -- fire up cdb: C:\Program Files\Debugging Tools for Windows (x64)>cdb -pn consoleapplication3.exe <SNIP> ModLoad: 000007fe`f7e90000 000007fe`f7eb4000 C:\Windows\Mi
Read more

Why do I keep getting exception code e0434352?

If you want to know how to debug CLR exceptions using cdb then read this post . Exception code e0434352 is the exception code used internally by the CLR to represent most exceptions(*). Regardless of if you throw a System.NullReferenceException or a System.ArgumentException in C#, you'll throw a SEH exception e0434352 under the covers. A fun way to validate this theory is to watch what happens to the CLR exceptions settings in cdb. Fire up cdb, and see the state of clr exceptions: 0:000> .shell -ci "sx" findstr clr clr - CLR exception - second-chance break - not handled clrn - CLR notification exception - break - handled .shell: Process exited Now, set the exception handler for exception number e0434352 and recheck the value of the clr exception handler: 0:000> sxe e0434352 0:000> .shell -ci "sx" findstr clr clr - CLR exception - break - not handled clrn - CLR notification exception - break - handled .shell: Process exited Armed with
Read more

Powershell script to enable windows to capture localhost traffic in wireshark

If you want to understand why the following scripts work read this post . Otherwise just paste the following into an elevated powershell window: Setup windows networking to allow localhost capturing in wireshark: # Find the network configuration that has the default gateway. $defaultAdapter = Get-WMIObject Win32_NetworkAdapterConfiguration | ? {$_.DefaultIPGateway} if (@($defaultAdapter).Length -ne 1) {throw "You don't have 1 default gateway, your network configuration is not supported" } # Route local IP address via the default gateway route add $defaultAdapter.IPAddress[0] $defaultAdapter.DefaultIPGateway Write-Host "Start capturing on localhost by connecting to $($defaultAdapter.IPAddress[0])" Return windows networking to normal configuration: # Find the network configuration that has the default gateway. $defaultAdapter = Get-WMIObject Win32_NetworkAdapterConfiguration | ? {$_.DefaultIPGateway} if (@($defaultAdapter).Length -ne 1) {throw "Y
Read more