On today's Day Two Cloud podcast, Rob Hirschfeld joins us to examine the challenges of working in edge environments. Many of those challenges include the infrastructure itself: how to provision, configure, and operate equipment in remote locations, how to ensure logical and physical security, and how to manage it all remotely.
The post Day Two Cloud 030: The Gnarly Challenges Of Edge Computing appeared first on Packet Pushers.
It’s been a while but we’re back and it feels great. In this episode I talk about the status of the show, where the heck I’ve been, and where we are headed. I also share my personal story on burnout and some of the lessons I learned along the way.
In the episode I mention the fantastic Denise Fishburn and a video she did on burnout that helped me realize what I was dealing with. That video is embedded below.
Outro Music:
Danger Storm Kevin MacLeod (incompetech.com)
Licensed under Creative Commons: By Attribution 3.0 License
http://creativecommons.org/licenses/by/3.0/
The post We’re Back appeared first on Network Collective.
This article was originally published as part of Perf Planet's 2019 Web Performance Calendar.
Have you ever wanted to quickly test a new performance idea, or see if the latest performance wisdom is beneficial to your site? As web performance appears to be a stochastic process, it is really important to be able to iterate quickly and review the effects of different experiments. The challenge is to be able to arbitrarily change requests and responses without the overhead of setting up another internet facing server. This can be straightforward to implement by combining two of my favourite technologies : WebPageTest and Cloudflare Workers. Pat Meenan sums this up with the following slide from a recent getting the most of WebPageTest presentation:
So what is Cloudflare Workers and why is it ideally suited to easy prototyping of optimizations?
From the documentation :
Cloudflare Workers provides a lightweight JavaScript execution environment that allows developers to augment existing applications or create entirely new ones without configuring or maintaining infrastructure.A Cloudflare Worker is a programmable proxy which brings the simplicity and flexibility of the Service Workers event-based fetch API from the browser to the edge. This allows a worker to Continue reading
Toward the end of 2019, a flurry of announcements by some of the most prominent IT companies suggests that collaborations will become increasingly important in the quantum computing space as the players jockey for position in the nascent market. …
Quantum Computing Providers Pick Their Dance Partners was written by Michael Feldman at The Next Platform.
I should have known better, but I couldn’t resist being pulled into a Twitter spat around the question “whether networking engineers need to know something about math” a long while ago.
Before going into the details, let’s start with Wikipedia definition: “Engineering is the use of scientific principles to design and build machines, structures, and other things” including “specific emphasis on particular areas of applied mathematics, applied science, and types of application”.
So feel free to believe that you don’t need any math or other science (because there’s very little science behind what we do in networking) in your job, in which case you might want to stop reading… but then at least please think twice about your job title.
Read more ...Ironies of automation, Bainbridge, Automatica, Vol. 19, No. 6, 1983
With thanks to Thomas Depierre for the paper recommendation.
Making predictions is a dangerous game, but as we look forward to the next decade a few things seem certain: increasing automation, increasing system complexity, faster processing, more inter-connectivity, and an even greater human and societal dependence on technology. What could possibly go wrong? Automation is supposed to make our lives easier, but ~~if~~ when it goes wrong it can put us in a very tight spot indeed. Today’s paper choice, ‘Ironies of Automation’ explores these issues. Originally published in this form in 1983, its lessons are just as relevant today as they were then.
The central irony (‘combination of circumstances, the result of which is the direct opposite of what might be expected’) referred to in this paper is that the more we automate, and the more sophisticated we make that automation, the more we become dependent on a highly skilled human operator.
Why do we automate?
The designer’s view of the human operator may be that the operator is unreliable and inefficient, so should be eliminated from the system.
An automated system Continue reading
"Using the software layer to address not just the security but also the cost element, the cost...
The platform is designed to run on any x86-based white box. However, the company has partnered with...
In part 1 of the GitOps blog series, we discussed the value of using GitOps for Calico policies, and how to roll out such a framework. In this second part of the series, we will expand the scope to include decentralized deployment and GitOps.
We see different personas among our customers deploying three types of controls:
This is different from the traditional firewall world, where the security admin is responsible for managing security policies, and the change management window could be several weeks in duration. Adopting that model in Kubernetes is simply counter to the very principles of enabling the developers. So how can we make policy creation and enforcement simple, yet adhere to organizational processes? The answer lies in simple tooling, GitOps and governance.
Policies have business logic that must be implemented in YAML. The business logic (allow access for service A to service B, open port 443 inbound on service B, permit access to slack webhook Continue reading
In part 1 of the GitOps blog series, we discussed the value of using GitOps for Calico policies, and how to roll out such a framework. In this second part of the series, we will expand the scope to include decentralized deployment and GitOps.
We see different personas among our customers deploying three types of controls:
This is different from the traditional firewall world, where the security admin is responsible for managing security policies, and the change management window could be several weeks in duration. Adopting that model in Kubernetes is simply counter to the very principles of enabling the developers. So how can we make policy creation and enforcement simple, yet adhere to organizational processes? The answer lies in simple tooling, GitOps and governance.
Policies have business logic that must be implemented in YAML. The business logic (allow access for service A to service B, open port 443 inbound on service B, permit access to slack webhook Continue reading
The business unit had a long list of “potential suitors,” said Symantec’s John Lioanto....
A system is more than its central processor, and perhaps at no time in history has this ever been true than right now. …
Intel Declares A Truce Before Bus Wars Flare Up was written by Timothy Prickett Morgan at The Next Platform.
When many think of the Internet of Things (IoT) and connected vehicles from a compute perspective, the first thing that springs to mind is likely the small processors that are hard at work sensing, analyzing, and feeding data to remote systems. …
How HPC, AI, and IoT Drive the Future of Smarter Vehicles was written by Nicole Hemsoth at The Next Platform.
“These technologies are not standalone technologies, they’re actually reinforcing,” Intel CEO...