Design resilient software systems by adopting architectural patterns, observability techniques, and disaster recovery strategies that ensure high availability and graceful degradation under failure.
From this track
How to Find Resilience Bugs in Systems that Don't Exist
Wednesday Mar 18 / 10:35AM GMT
Building correct distributed systems takes thinking outside the box, and the fastest way to do that is to think inside a different box. One different box is "formal methods", the discipline of mathematically verifying software and systems.
Hillel Wayne
Author of "Logic for Programmers" and "Learn TLA+", Thought Leader in the Space of Empirical Software Engineering
Spritely: Infrastructure for the Future of the Internet
Wednesday Mar 18 / 11:45AM GMT
Let's take back the internet! Learn about Spritely's work to re-decentralize the net with new foundational technologies that put users in control.
Christine Lemmer-Webber
Executive Director @Spritely Institute, Co-Author of ActivityPub
David Thompson
CTO @Spritely Institute
Understanding Progressive Collapse: How To Avoid A Cascading Failure
Wednesday Mar 18 / 01:35PM GMT
Small things going wrong can quickly snowball. The cascading failure is often a nightmare scenario for any system. An initial problem, which in isolation seems like such a minor problem, can kick off a chain reaction of ever-increasing failures, potentially leading to catastrophic results.
Sam Newman
Microservice, Cloud, CI/CD Expert, Author of "Building Microservices" and "Monolith to Microservices", 20+ Years Experience as a Developer
Maintaining Data Integrity During Regional Outages
Wednesday Mar 18 / 02:45PM GMT
Details coming soon.
Migrating Legacy Monoliths to Resilient Microservices Without Downtime
Wednesday Mar 18 / 03:55PM GMT
Details coming soon.
