This is the blog of Ronald Bartels that wanders on and off the subject of problem management (that is how it started). Mostly now the topics are about IoT and SD-WAN.
Search This Blog
Resilience Engineering: Part I
I’ve been drafting this post for a really long time. Like most posts,
it’s largely for me to get some thoughts down. It’s also very related
to the topic I’ll be talking about at Velocity later this year. When I gave a keynote talk at the Surge Conference last year,
I talked about how our field of web engineering is still young, and
would do very well to pay attention to other fields of engineering,
since I suspect that we have a lot to learn from them. Contrary to
popular belief, concepts such as fault tolerance, redundancy of
components, sacrificial parts, automatic safety mechanisms, and capacity
planning weren’t invented with the web. As it turns out, some of those
ideas have been studied and put into practice in other fields for
decades, if not centuries. Systems engineering, control theory, reliability engineering…the list
goes on for where we should be looking for influences, and other folks
have noticed this as well. As our field recognizes the value of taking a “systems” (the C. West Churchman definition, not the computer software definition) view on building and managing infrastructures with a “Full Stack Programmer”
perspective, we should pull our heads out of our echo chamber every now
and again, because we can gain so much from lessons learned elsewhere.
Firewalls are becoming increasingly important in today’s world. Hackers and automated scripts are constantly trying to invade your system and use it for Bitcoin mining, botnets or other things. To prevent these attacks, you can use a firewall on your system. IPTables is the strongest firewall in Linux because it can filter packets in the kernel before they reach the application. Using IPTables is not very easy for Linux beginners. We have created easywall - the simple IPTables web interface . The focus of the software is on easy installation and use. Access this neat software over on github: easywall
When building a DDoS mitigation service it’s incredibly tempting to think that the solution is scrubbing centers or scrubbing servers. I, too, thought that was a good idea in the beginning, but experience has shown that there are serious pitfalls to this approach. Read the post of at Cloudflare's blog: N o Scrubs: The Architecture That Made Unmetered Mitigation Possible
Comments
Post a Comment