
SD-WAN has finally arrived. We’re not longer talking about it in terms of whether or not it is a thing that’s going to happen, but a thing that will happen provided the budgets are right. But while the concept of SD-WAN is certain, one must start to wonder about what’s going to happen to the providers of SD-WAN services.
I’ve written a lot about SDN and SD-WAN. SD-WAN is the best example of how SDN should be marketed to people. Instead of talking about features like APIs, orchestration, and programmability, you need to focus on the right hook. Do you see a food processor by talking about how many attachments it has? Or do you sell a Swiss Army knife by talking about all the crazy screwdrivers it holds? Or do you simply boil it down to “This thing makes your life easier”?
The most successful companies have made the “easier” pitch the way forward. Throwing a kitchen sink at people doesn’t make them buy a whole kitchen. But showing them how easy and automated you can make installation and management will sell boxes by the truckload. You have to appeal the opposite nature that Continue reading
Both provide an alternative to traditional IT infrastructure integration, but take different approaches.
I appreciated this rant by @alicegoldfuss on a impractical parts of running containers. Not many people talk about the downsides.
(shame its not on a blog somewhere where it would be readable)
It's almost like containers only improved the Dev side of DevOps hmmmm how strange
— Alice Goldfuss (@alicegoldfuss) January 26, 2017
Hope none of your containers have noisy neighbors because cgroups only go so far.
— Alice Goldfuss (@alicegoldfuss) January 26, 2017
Iptables? Different with containers? Perf profiling? Much harder with containers.
— Alice Goldfuss (@alicegoldfuss) January 26, 2017
Hope none of your containers have noisy neighbors because cgroups only go so far.
— Alice Goldfuss (@alicegoldfuss) January 26, 2017
Orchestrators can redeploy a dead instance but can they detect latency and move it to a better system? Because a slow container is hell.
— Alice Goldfuss (@alicegoldfuss) January 26, 2017
Everyone using containers means I don't have to wake someone else up to deploy their broken shit. It makes DR much faster, too.
— Alice Goldfuss (@alicegoldfuss) January 26, 2017
But that's only half of the ol DevOps pie. The other half? More burden and work. At scale.
— Alice Goldfuss (@alicegoldfuss) January 26, 2017
Why do Continue reading