Code writing is hard, but defining the scope of the project may be even harder.
Whether they are cloud or premise based, not all vCPE elements are identical. Learn more during the December 9th webinar with Brocade.
Last night, Plexxi received the Product of the Year Award from the New Hampshire High Tech Council. More than 200 people, including New Hampshire Governor Maggie Hassan, were on hand as we received the award for our Switch 2 solution. We’re proud to be recognized by an organization that values the advancement of innovation throughout the state of New Hampshire. Plexxi is committed to growing the local tech economy by producing dynamic solutions and hiring the best talent the state has to offer. Congratulations to all of the finalists and companies that are dedicated to shaping an ecosystem for technology companies to grow and succeed in New Hampshire.
Pictured Left to Right: Peter Antoinette, co-founder, president and CEO of Nanocomp Technologies, and prior Product of the Year Award winner; Paul Mailhot, VP of Business Operations at Dyn and chairman of the Council’s board of directors; Michael Welts, VP of Marketing at Plexxi; Toral Cowieson, Senior Director of Internet Leadership at the Internet Society and the Council’s vice chair; and Matt Cookson, president of Cookson Strategies and the Council’s Executive Director.
Our CEO Rich Napolitano penned a byline this week in ITProPortal that chronicles the past three “eras” of IT, and Continue reading
Executing a winning strategy.
Hey, it's HighScalability time:
The Packet Pushers share perspectives on job interviews. They talk about how to prepare, discuss the what an interviewer is really thinking, and offer tips on getting ready for the technical and non-technical portions of the interview.
The post Show 263: The Job Interview Process appeared first on Packet Pushers.
Contrary to folk wisdom, ignorance is usually not blissful. Generally, it produces the very opposite of bliss. Just ask the frightened hiker lost in some remote mountain blizzard who never paid attention to his Boy Scout instruction; or ask the new employee who never did her math homework, frantically trying to figure out the correct change for customers; or, worse yet, ask the frustrated and annoyed patrons waiting in the ever-increasing line as this new employee bumbles one purchase after another.
Phillip Dow, Virtuous Minds
The post QOTW: Ignorance appeared first on 'net work.
The post Worth Reading: The Cryptech Project appeared first on 'net work.
Please join us in congratulating the following iPexpert students who have passed their CCIE lab!
One of the key decisions in designing a compute infrastructure is how to handle networking.
For platforms that are designed to deliver applications, it is now common knowledge that application developers need a platform that can execute and manage containers (rather than VMs).
When it comes to networking, however, the choices are less clear. In what scenarios are designs based on single layer preferable vs. overlay networks ?
The answer to this question is not a simplistic one based on “encapsulation overhead”; while there are overlay networking projects that do exhibit poor performance, production ready solutions such as OpenContrail have performance characteristics on both throughput and PPS similar to the Linux kernel bridge implementation. When not using an overlay, it is still necessary to use an internal bridge to demux the container virtual-ethernet interface pairs.
The key aspect to consider is operational complexity!
From a bottoms-up perspective, one can build an argument that a network design with no encapsulation that simply uses an address prefix per host (e.g. a /22) provides the simplest possible solution to operate. And that is indeed the case if one assumes that discovery, failover and authentication can be handled completely at the “session” layer (OSI model).
I’m familiar with a particular compute infrastructure where this is the Continue reading
Imagine you’d design your network by documenting the desired traffic flow across the network under all failure conditions, and only then do a low-level design, create configurations, and deploy the network… while being able to use the desired traffic flows as a testing tool to verify that the network still behaves as expected, both in a test lab as well as in the live network.
Read more ...