Rating is available when the video has been rented.
This feature is not available right now. Please try again later.
Published on Sep 3, 2015
In the final webinar with live Q/A in the Reactive Revealed series, we explore the way that Reactive systems maintain resiliency with an infrastructural approach designed to welcome failure often and recover gracefully. Presented by Reactive Manifesto co-author, Akka creator and CTO at Typesafe, Inc., Jonas Bonér explores what you should know about:
What you should know about maintaining resiliency with monolithic systems compared to distributed systems
How Reactive systems handle errors and prevents catastrophic failures with isolation and containment, delegation and replication
How isolation (and containment) of error state and behavior works to block the ripple effect of cascading failures
How delegation of failure management and replication lets Reactive systems continue running in the face of failures using a different error handling context, on a different thread or thread pool, in a different process, or on a different network node or computing center