Reactive for DevOpsPart 4: Using ConductR to maintain system

resiliency and improve elasticitywith Markus Jura

Reactive for DevOps

Agenda

• Elasticity

• Masterless architecture

• Load balancing

• Akka cluster awareness

• Resiliency

• Failure detection

• Consolidated logging

• Bundle monitoring

2

Elasticity

Reactive for DevOps

Masterless architecture

4

Reactive for DevOps

Load balancing

5

• ConductR has support for load balancing built in through HAProxy

• Additional load balancer on top possible

Reactive for DevOps

Akka cluster awareness

• ConductR automatically configures seed nodes

• Identifies if cluster has been created

• Overwriting configuration during bundle startup

• No need to hard-code seed node addresses in configuration

6

Resiliency

Reactive for DevOps

Failure detection

• Any ConductR node can perform any operation

• No single point of failure

• Restarting bundles in case of node crashes

• Restarting failed bundles

• Auto detection of split brain scenarios

8

Reactive for DevOps

Consolidated logging

• ConductR consolidates log messages of all nodes

• By default Elasticsearch and Kibana is used to display log messages

• Other logging tools can be plugged-in

9

Reactive for DevOps

Bundle monitoring

• Bundle signals health

• ConductR retrieves events to automatically scale up or down

• Coming up in Q4 2015

10

Demo

REACTIVE PLATFORMFull Lifecycle Support for Play, Akka, Scala and Spark

Give your project a boost with Reactive Platform:

• Monitor Message-Driven Apps • Resolve Network Partitions Decisively • Integrate Easily with Legacy Systems • Eliminate Incompatibility & Security Risks • Protect Apps Against Abuse • Expert Support from Dedicated Product Teams

Enjoy learning? See about the availability of on-site training for Scala, Akka, Play and Spark!

Learn more about our offersCONTACT US