Quantcast

Blog

Merchant Silicon and Lawnmowing Revisited

October 21, 2009
Filed Under: in Analysis, Infrastructure 2.0
Author: Douglas Gourlay

image Chance had it that today a friend of mine sent me an email reminding me of a blog post I wrote about a year and a half ago titled - 'On Merchant Silicon and Mowing my Yard.'  It was a piece, purposefully a bit inflammatory, designed to have a bit of a go at the guys who were drawing some interesting comparisons to product lines I worked on.

If a switch is like a car then the switching silicon would be most analogous to the engine and/or transmission.  For example, the core of the car and a major point of competitive advantage and differentiation.  Do major automobile manufacturers outsource engine design and development to other firms? 

Of course not, they design and build their engines.  Do manufacturers of more consumer goods like lawn mowers outsource their engines? 

Absolutely, they go to specialized engine manufacturers because the core value of what they offer is either a certain price point, or the value is not tied to the engine.

So the question then become: do you want to ride to work or school in a car, or on a lawnmower?  I know one would get me laughed at if I was in school, the other… not so much.

Applying it back to switching: I’d rather control my own destiny and align the core value creation in the silicon with the hardware and then with the software and continue to drive innovation at every tier and not saddle up on my Toro in my enterprise. 

(no offense to the manufacturer of lawn mowers, I am a good customer of yours too).

As often happens, times change.

image Reading this email which spoon-fed my prior writings back to me, I had to reflect a bit.  Does merchant silicon matter?  Is it a sell out?  What creates customer value in a networking product?  Is it the silicon, the software, the system as a whole, how it operates with other adjacent products…

Realistically, to me, what most people seem to care about in a switch is that it works, at the performance rates necessary, and that the software is stable and has the features they need to accomplish the networking task at hand.

Inside this system there is a collection of silicon, some of which may be custom, some which comes from vendors other than the systems manufacturer.  The PHYs are almost always third party, the CPUs as well, most every part is always 'merchant silicon' except the switch fabric and the packet processor.  These are custom in some switches, or merchant in others depending on that specific vendors goals for that particular product.

Ethernet continues to evolve and offers lots of opportunities for innovation and improvement - some of these will require new silicon, some will require new software.  Using merchant silicon sometimes will affect a vendors ability to control the pace and order they bring features to market that require new silicon.  However, with the breadth of silicon available in the market today there are several viable silicon choices.

Custom chips create their own set of challenges - most vendors doing their own chips actually do their own logic and rely on a third party to actually build the chips and fab them out, deal with the process challenges, etc.  The vendors doing full custom take on a high cost burden up front and hope they get enough market traction to enable future R&D in their ASIC teams.  In this period of compressed budgets these programs tend to be one of the first things to get financial focus.   

What do you think- is one better than the other, or is a healthy mix appropriate for our maturing industry?

Oh, and I since outsourced yard mowing...  too time consuming and others did a better job than I ever could.

[Editor’s Note: Welcome back SiliconANGLE contributor and Veep of Marketing for Arista Networks Douglas Gourlay. He’s been on vacation the last couple of weeks, but is back on the job now. This post originally appeared on his personal blog. –mrh]

Related Conversations