what is reactive

Being Reactive is GoodKevin Webber, Enterprise Advocate, Lightbend

Problem?» we used the right tools to build the wrong thing


» proactive isn't always good


» proactive isn't always good

» reactive isn't always bad

» let principles guide our

» design

» tool selection

» implementation choices


» design

» tool selection


» principles should be accessible and universal


» design

» tool selection


» principles should be accessible and universal

» principles should help people

» reactive helps engineers, lines of business, and enterprises to capture opportunities

What is Reactive?

asynchronous, non-blocking, real-time, highly-available, loosely coupled, scalable, fault-tolerant, concurrent, reactive, event-driven, push instead of pull, distributed, low latency, high throughput...

asynchronous, non-blocking, real-time, highly-available, loosely coupled, scalable, fault-tolerant, concurrent, reactive, event-driven, push instead of pull, distributed, low latency, high throughput...

Too complicated. We need a simple vocabulary.

Overview

» Lagom - Microservices framework

» Play - RESTful API framework

» Akka - Distributed computing toolkit

» Spark - General purpose compute engine

Akka Users

Reactive Principles

Message-driven» Akka provides all of the

building blocks of reactive systems

» distribution

» location transparency

» isolation

Resilient» supervision

Resilient» dedicated separate error

channel

Resilient» location transparency

» remoting and clustering

» references are stable

Resilient» location transparency

» senders can still emit events even when actors move from one location to another

Elastic» scale up

» async

» non-blocking

» scale out

» immutable data

» share nothing

Responsive» responsive to events

» events within the business (existing customers)

» events in the market (new opportunity)

» responsive to technology

» load, failure

» emerging technologies (reactive architecture)

» responsive to users

» responsivea request for service is always answered, even when failures occur

» elasticservices scale up and down on demand

» resilientservices recover from failures

» message drivenservices respond to the world, not attempt to control what it does

How do we build reactive systems?Applying the Reactive principles to build a fully reactive microservices system, using:

» The Lightbend Reactive Platform

» Third-party tools

» Existing infrastructure (hybrid-cloud, etc)

Fast Data Architecture» Akka Streams

» 1-10 second latency per-event processing

» Spark Streaming

» 10+ second mini-batch event processing

» Streams become the glue of the organization

Heritage Modernization» Carve up a monolith

» Akka and Play are general purpose, powerful toolkits well suited to enterprise environments

» Java, Scala, JVM

MSA» Push-streaming or pub-sub

for service-to-service messaging

» API gateway in front of the MSA for consumers

» Aggregation

» Authentication/authorization

» Protocol conversion

» Etc

Thank you!Kevin Webber

Medium: medium.com/@kvnwbbrTwitter: @kvnwbbr

Point of contact

[email protected]

what is reactive

Technology