Building Reactive Applications with Akka Jonas Bonér Typesafe CTO & co-founder @jboner This is an era of profound change. Implications are massive, change is unavoidable Users Applications Businesses ! ! ! ! ! ! ! ! ! Users are demanding richer and Mobile and HTML5; Data and Businesses are being pushed to more personalized experiences. compute clouds; scaling on react to these changing user ! demand. expectations… ! ! Yet, at the same time, expecting blazing fast load time. Modern application technologies ...and embrace are fueling the always-on, real- modern application time user expectation. requirements. ! ! ! ! ! ! ! Reactive Applications 3 As a matter of necessity, businesses are going Reactive. Reactive applications share four traits Reactive Applications 5 Reactive applications react to changes in the world around them. Event-Driven • Loosely coupled architecture, easier to extend, maintain, evolve • Asynchronous and non-blocking • Concurrent by design, immutable state • Lower latency and higher throughput “Clearly, the goal is to do these operations concurrently and non-blocking, so that entire blocks of seats or sections are not locked. We’re able to find and allocate seats under load in less than 20ms without trying very hard to achieve it.” Andrew Headrick, Platform Architect, Ticketfly 7 Introducing the Actor Model. The Actor Model 9 The Actor Model A computational model that embodies: 9
Description: