Introducing ConductR 1.0

This past March, we announced the upcoming release of a new Operations tool in a post named Welcome to the Typesafe family, ConductR! Since then, we've triple-checked everything and are now happy to announce the general availability of ConductR v1.0, with which production users of Java or Scala and Typesafe Reactive Platform technologies–Play, Akka or Slick–are now able to experiment in an interactive, managed evaluation. If you want to get right to it:

  1. Check out the ConductR Evaluation Guide (PDF).

  2. Sign up for our May 27th webinar "Evaluating Typesafe ConductR".

  3. Go right for it and visit the ConductR Evaluation sign-up page now.

​Otherwise, please read on!

A little background: Why Ops needs tools for distributed, Reactive applications

Reactive application development is no longer used only by a handful of visionary, early adopters. As outlined in the Reactive Manifesto, developing these message-drivenelasticresilient and highly responsive applications is what’s fueling the new wave of systems that are deployed on everything from mobile devices to cloud-based clusters running thousands of multi-core processors. Recently, the launch of Reactive Streams 1.0.0 supports this movement by addressing the challenge to "provide a standard for asynchronous stream processing with non-blocking back pressure." Many passionate engineers from Typesafe, Netflix, Pivotal, Red Hat, Oracle, MongoDB and others have contributed.

So where do all these trail-blazing efforts leave Operations teams? Up at night, in a way. Hence our purpose in creating ConductR, Typesafe's first commercial product to complement the open source technologies available in the Typesafe Reactive Platform.

Typesafe ConductR in a nutshell

Typesafe ConductR is a Reactive Application Manager designed to make it more convenient for Operations to deploy and manage Reactive applications, focused on handling distributed applications and microservices

ConductR is meant to handle clusters by default, designed to talk to many services and machines. While ConductR is not meant to manage infrastructure (rather working with your existing infrastructure tools like Amazon EC2, Mesos, Docker, Ansible, Chef, Puppet, etc.), ConductR focuses on the live services and applications themselves, wherever they are in your cluster. ConductR's reason for being is to let Operations more conveniently enforce your Reactive system's already-built-in responsiveness, resilience and elasticity at scale in the face of bursty traffic or multiple service failures. Controlled through a familiar CLI, ConductR also provides a simple visualizer to give a real-time view of what's running and where:

ConductR moves beyond running multiple instances of the services that are your applications and trying to make it all resilient. With ConductR, we deploy applications in the form of archives of components together with their configuration metadata to the cluster. ConductR is a deployment target for the next generation of applications as we continue the progression up the infrastructure stack from bare hardware, to virtual machines, to IaaS and now clusters.

What a "managed" evaluation process means for you

Evaluating ConductR might not be like other technology trials you've experienced before.

ConductR is a commercial product designed for Typesafe Reactive Platform users, so it is currently restricted to teams running Java or Scala apps along with Play, Akka or Slick in a production environment. Trying ConductR is an interactive, 2-week evaluation process designed to rapidly help evaluators get up and running and decide if ConductR is for you now, next month, next quarter etc.

The purpose of a managed evaluation is to rapidly explore ConductR in a three-part, hands-on process with goals to achieve before moving forward to the next stage. If doing this in two weeks is too ambitious, don’t worry–we’re happy to work with your schedule. The three stages are:

  1. Installation

  2. Implementation

  3. Experimentation

In addition to a public webinar on May 27th (see below), we've put together an evaluation guide in a PDF for you to review the stages, expectations and goals in more detail.


Webinar May 27th 9:00 PST: "Evaluating Typesafe ConductR, a Reactive Application Manager"

Learn exactly how to get started with the ConductR evaluation in this 1-hour guided webinar with VP of Engineering, Derek Henninger and Ed Callahan, Senior Software Engineer. If you can't make it, don't worry: it will be recorded. In the meantime, feel free to check out the ConductR demo video at the top of this post, or go for the recorded video from the previous webinar, featuring tech lead Christopher Hunt introducing ConductR for the first time.


How to evaluate ConductR now 

At the risk of sounding repetitive, we want to again state that the ConductR 1.0 evaluation is currently available only to production users of Java or Scala and Typesafe Reactive Platform technologies Play, Akka or Slick. If you aren’t currently using these technologies in production, then ConductR is not for you quite yet–but we invite you to check out these Typesafe Reactive Platform resources to get an idea of the foundation of it all. If Typesafe Reactive Platform is already your friend, then the ConductR Evaluation Guide (PDF) is the first place to go to figure out if this evaluation is right for you at this time. Alternatively, you can request to be contacted by a Typesafe representative for more information. 

If it's all systems go, continue here to begin your journey with ConductR! 




View All Posts or Filter By Tag



Austin (TX) - October 18-20


Reactive Microservices Architecture

by Jonas Bonér


Fast Data Architectures For Streaming Applications

by Dean Wampler


Designing Reactive Systems: The Role Of Actors In Distributed Architecture

by Hugh McKee


Developing Reactive Microservices

by Markus Eisele


Enterprise Development Trends 2016

Cloud, Container and Microservices Insights from 2100 JVM Developers


Lightbend Reactive Platform

A High-Level Technical Overview For Decision Makers