A Reactive Application Manager that lets Operations conveniently deploy and manage distributed systems

ConductR is the easiest way for both Dev and Ops to deploy Reactive applications and microservices

What is Typesafe ConductR?• A Reactive Application Manager that lets Operations

conveniently deploy and manage distributed systems

• ConductR helps Operations orchestrate their Reactive application deployment to a cluster, quickly scaling in and out while ensuring responsiveness, resilience and elasticity of the system during the rollout.

3Go Reactive

4

Go Reactive 5

Manage a Cluster, not a Server• Without ConductR• Without ConductR

• Build machines / nodes with application stack• OS• App Server• Apps• App lifecycle (start, stop, etc)

• Add resilience• Config load balancer• Config port

• With ConductR• Build machines / nodes with

ConductR• OS• ConductR

• Deploy applications / services to cluster via ConductR

Resilient from the core, not as an add-on

Cluster from the ground upReactive from the ground upResilient from the ground up

7

8

Go Reactive 9

DevOps friendly

Bundles contain application / service and isolated configuration parameters

Go Reactive 10

Bundle Lifecycle• Load

• Run• Scale

• Stop

• Unload

Go Reactive 11

• Works with your existing infrastructure & provisioning automation tools:• Amazon EC2, Docker, Ansible, Chef, Puppet, etc.

• Orchestrates deployment of application bundle instances on provisioned nodes

• Enables rapid scaling in and out

Cluster

Go Reactive 12

Resilient

• Isolated and redundant bundle instances

• Because distributed, any node can take on any responsibility

• Multiple instances provide redundancy

• Failure remains isolated within each bundle

• Parts can fail and recover without compromising the system as a whole

• Asynchronous libraries with back-pressure detection mechanisms

Go Reactive 13

• Distributes bundle instances to wherever resources are known to be available

• Bundle instances can start immediately

• Uses proven technologies, like HAProxy

• Consolidated logging so Ops knows what’s going on

Elastic and Responsive

Go Reactive 14

• Reactive applications are loosely coupled, so location information is not hardcoded

• Dynamic service discovery finds the service name and provides an address

• Services come and go with no impact on running application / service

Discover

Go Reactive 15

Business Benefits • Reduce costs

• Higher utilization of compute resources• Replace time-consuming error prone activities and expensive

home-grown tooling with automation designed specifically for Reactive applications

• Mitigate risk• Achieve resilience across your entire deployment cycle

• Improve productivity• Ops team can deploy & manage reactive applications quickly and

efficiently• Application reliably deploys same way every time• Reduce maintenance efforts

Go Reactive 16

ConductR is a no-brainer if:• You are using Akka Cluster

• You are using AWS• Especially if running on multiple Availability Zones, where

connectivity loss between AZs is common• Attempting to solve with Zookeeper

Go Reactive 17

Evaluate ConductR if:• You are using Typesafe Reactive Platform (Akka,

Play, or Scala)• Note: ConductR also support non RP apps, including non

JVM applications

• You have 3 or more nodes in your deployment

Go Reactive 18

Suggested Next Steps

WHITE PAPER

Typesafe ConductRWhite Paper

GET WHITE PAPER

DEMO

Typesafe ConductRDemo

WATCH NOW

GUIDE

Typesafe ConductREvaluation Guide

DOWNLOAD NOW