Worth Reading: Resilience Engineering
Starting with my faking disaster recovery tests blog post Terry Slattery wrote a great article delving into the intricacies of DR testing, types of expected disasters, and resilience engineering. As always, a fantastic read from Terry.
Recent posts in the same categories
design
- EVPN Designs: EVPN EBGP over IPv4 EBGP
- EVPN Designs: EBGP Everywhere
- One-Arm Hub-and-Spoke VPN with MPLS/VPN
- EVPN Hub-and-Spoke Layer-3 VPN
- Hub-and-Spoke VPN on a Single PE-Router
- Hub-and-Spoke VPN Topology
data center
- Response: The Usability of VXLAN
- Migrating a Data Center Fabric to VXLAN
- The Mythical Use Cases: Traffic Engineering for Data Center Backups
- Video: What Is Software-Defined Data Center
- Repost: L2 Is Bad
- Path Failure Detection on Multi-Homed Servers
Interesting article indeed.
But in my view what Terry is talking about is Reliability Engineering in general and how to apply those techniques to Network Engineering.
But what article doesn't describe is how to bridge the gap between IT and Computer Science in general. As we both know, IT works on top of abstraction and CS works on layers deep inside.
That's one of the reason in my view usually IT guys including Network Engineers though always talk about concepts such as Complexity, Reliability, High Availability and so forth, they don't necessarily understand what's working deep inside behind the scenes. But I guess they don't need to either as that's what separate IT from CS.
Based on my own analysis and trends in the industry today, somehow I feel CS is becoming more and more relevant as the stacks and solutions are getting more and more close to Application layer to solve some of old problems which otherwise Network and IT guys tried to solve at lower layers from OSI stack standpoint.
Thoughts ?
https://blog.ipspace.net/2018/12/bifurcation-of-knowledge.html