Beyond the Buzzword - a reactive application in practice

transcript

Beyond the buzzword:

a reac%ve web applica*on in prac*ce

Manuel Bernhardt - @elmanu

Slovak Scala Users' Group - May 2016

Slovak Scala Users' Group May 2016 - manuel.bernhardt.io - @elmanu

Agenda

1. Evolu(on of web applica(on architecture

2. Evolu(on of hardware

3. Small Reac(ve Web Applica(on

4. Deployment

If you have a ques-on, shoot!

Manuel Bernhardt

• I help established companies ge3ng started with using reac%ve applica%ons in their distributed systems infrastructure

• h9p://manuel.bernhardt.io

Manuel Bernhardt

• I help established companies ge3ng started with using reac%ve applica%ons in their distributed systems infrastructure

• h9p://manuel.bernhardt.io

A short (and mostly wrong)history of web applica1on

architectureSlovak Scala Users' Group May 2016 - manuel.bernhardt.io - @elmanu

"Good old days" architecture

"3 $er" architecture

"Cloud" architecture

"Microservices" architecture

"Microservices" = emerging architecture

Trend: increasing amount of network I/O

Reac%ve architectural pa/ern

Evolu&on of hardware

Evolu&on of CPUs

Evolu&on of memory

Conclusion

• many-core & distributed systems

• awesome hardware

• awesome so5ware? we need:

• explicit asynchronous programming

• explicit failure handling

Let's build a small Reac0ve Web Applica0on

Actors

• lightweight objects

• send and receive messages (mailbox)

• can have children (supervision)

"Long-lived" async computa5on

CODING

Futuresscala.concurrent.Future[T]

• holds a value of type T

• can either fail or succeed

• async code does not block a thread while wai8ng for comple8on

"Short-lived" async computa6on

Pipeakka.pattern.pipe

• bridge between Futures and Actors

• implemented as anonymous actor

Pipeakka.pattern.pipe

• bridge between Futures and Actors

• implemented as anonymous actor

Circuit Breakerakka.pattern.CircuitBreaker

• helpful when dealing with legacy / slow systems & prevents cascading failure

• like an electric circuit breaker, trips when there's a surge

• trips a=er a given number of failures, for a given >meout, then a?empts reset

DeploymentSlovak Scala Users' Group May 2016 - manuel.bernhardt.io - @elmanu

Deployment• stand-alone vs. "elas/c deployment"

• elas/c, fault-tolerant is not trivial

• use a managed service / solu/on

Deployment

• Lightbend ConductR

• automated cluster management for Play / Akka / ... applica>ons

• automated node failure & network par++on resolu+on

Deployment

• fully managed opera0ons

• auto scalability feature (horizontal & ver0cal)

• a<rac0ve pricing

Load tes)ngSlovak Scala Users' Group May 2016 - manuel.bernhardt.io - @elmanu

Gatling

• open-source load tes0ng framework

• built with Scala, Akka and Ne=y

• two phases: record and run

Gatling simula,on file// ...setUp( scn.inject( nothingFor(4 seconds), rampUsers(100) over(10 seconds), atOnceUsers(10), constantUsersPerSec(2) during(15 seconds) randomized, splitUsers(500) into ( rampUsers(50) over(10 seconds) ) separatedBy(2 seconds) ).protocols(httpProtocol))

Bees with machine guns

Configuring all the things

• Installing Python & bees with machine guns

• AWS console (keys, security group w/ SSH access)

• boto config file

Configuring all the things

~/.boto

[Credentials]aws_access_key_id = foobar1aws_secret_access_key = foobar2

[Boto]debug = 2

A"ack!

Thank you!Ques%ons & Comments ?

• h#p://manuel.bernhardt.io

• manuel@bernhardt.io

• @elmanu

Beyond the Buzzword - a reactive application in practice

Engineering