How VMware's own value got virtualized.
What a week. Some tech conferences I like, and others I love. Falling solidly in my "love" category, the Amazon team pulled off another great event with re:Invent 2015. Of course, the AWS product folks didn’t disappoint, either. (And neither did surprise re:Play party guest Zedd.)
We welcomed many hundreds of visitors to our booth during the three days. Over 200 shirts, many more Ansibulls, and every single sticker, luggage tag, and business card were gobbled up by excited Ansible users and Tower customers.
Perhaps the most entertaining part was to learn what people had to say:
Network Break 57 delves into Dell and EMC and looks at upheavals affecting Juniper, Cisco, and AT&T. We also run from a new Verizon zombie tracking cookie, and opine on the rest of the week's tech news.
The post Network Break 57: Vendor Upheaval, Zombie Cookies Bite appeared first on Packet Pushers.
For a long time now stateless services have been the royal road to scalability. Nearly every treatise on scalability declares statelessness as the best practices approved method for building scalable systems. A stateless architecture is easy to scale horizontally and only requires simple round-robin load balancing.
What’s not to love? Perhaps the increased latency from the roundtrips to the database. Or maybe the complexity of the caching layer required to hide database latency problems. Or even the troublesome consistency issues.
But what of stateful services? Isn’t preserving identity by shipping functions to data instead of shipping data to functions a better approach? It often is, but we don’t hear much about how to build stateful services. In fact, do a search and there’s very little in the way of a systematic approach to building stateful services. Wikipedia doesn’t even have an entry for stateful service.
Caitie McCaffrey, Tech Lead for Observability at Twitter, is fixing all that with a refreshing talk she gave at the Strange Loop conference on Building Scalable Stateful Services (slides).
Refreshing because I’ve never quite heard of building stateful services in the way Caitie talks about building them. You’ll recognize most of the Continue reading
The post Worth Reading: Hybrid Infrastructure appeared first on 'net work.
This vendor-written tech primer has been edited by Network World to eliminate product promotion, but readers should note it will likely favor the submitter’s approach.
From Target to Ashley Madison, we’ve witnessed how interconnections with third-party vendors can turn an elastic environment -- where devices, services and apps are routinely engaging and disengaging -- into a precarious space filled with backdoors for a hacker to infiltrate an enterprise’s network. Here are the top five threats related to working with 3rd parties:
Threat #1 - Shared Credentials. This is one of the most dangerous authentication practices we encounter in large organizations. Imagine a unique service, not used very frequently, requiring some form of credential-based authentication. Over time, the users of this service changes, and for convenience considerations, a single credential is often used. The service is now accessed from multiple locations, different devices and for different purposes. It takes just one clumsy user to fall victim to one {fill in the credential harvesting technique of your choice}, to compromise this service and any following user of that service.
To read this article in full or to leave a comment, please click here
The 2015 Layer 123 SDN & OpenFlow World Congress will be available live on Monday October 13th and Tuesday October 14th. Watch the live stream of the event for free on SDxCentral.
ClearPath leverages HP's virtual network functions (VNFs) together with its own vCPE technology to target service providers.
It’s common enough in the networking industry — particularly right now — to bemoan the rate of change. In fact, when I worked in the Cisco Technical Assistance Center (TAC), we had a phrase that described how we felt about the amount of information and the rate of change: sipping through the firehose. This phrase has become ubiquitous in the networking world to describe the feeling we all feel of being left out, left behind, and just plain not able to keep up.
It’s not much better today, either. SDNs threaten to overturn the way we build control planes, white boxes threaten to upend the way we view vendor relationships, virtualization threatens to radically alter the way we think about the relationship between services and the network, and cloud computing promises just to make the entire swatch of network engineers redundant. It’s enough to make a reasonable engineer ask some rather hard questions, like whether it’s better to flip burgers or move into management (because the world always needs more managers). Some of this is healthy change, of course — we need to spend more time thinking about why we’re doing what we’re doing, and the competition of the cloud Continue reading
Cash, debt, and a tracking stock back what might be the biggest tech acquisition ever.
Network Insight Blogger and industry guru, Matt Conran, featured Plexxi in his October 6 post Application-aware Networking-Plexxi Networks. He believes, “Mobility and dynamic bandwidth provisioning force us to rethink how we design networks.” We agree.
Conran defines application-aware networking as the idea that application visibility combined with network dynamism will create an environment where the network can react to the changing behavior of application mobility and bandwidth allocation requirements. With that in mind, he took a comprehensive look at what we’ve been doing to “reverse the traditional design process and let the application dictate what kind of network it wants.”
Conran states that, “Networks should be designed around conversions but when you design a network it is usually designed around reachability. A conversational view measures network resources in a different way, such as application SLA and end-to-end performance. The focus is not just uptime. We need a mechanism to describe applications in an abstract way and design the network around conversations. The Plexxi affinity model is about taking a high-level abstraction of what you want to do, let the controller influence the network and take care of the low-level details. Affinity is a policy language that dictates exactly how you want the network to Continue reading