Optimised for Typesafe Reactive Platform

Typesafe announces ConductR, a management tool for Reactive systems

JAXenter Editorial Team
Typesafe ConductR via Typesafe

The company behind the Play framework, Akka and Scala has unveiled a new management tool for distributed deployment and management of microservice-based Reactive applications.

Existing infrastructure and automation tools tend to focus on “traditional” monolithic application architectures and usually just about meet the needs of today’s distributed applications (and sometimes not at all).

For this reason, operators often have to rely on either “homemade” solutions and proprietary and open-source tools patched together. And that can often be costly. These kinds of environments have the added disadvantage of making practical service level agreements increasingly difficult or even impossible.

This is right where Typesafe want ConductR to enter. The idea behind the tool is to help users meet the challenges that arise when deploying and managing (long-term) Reactive applications in distributed environments.

SEE ALSO: Why the Reactive future on the JVM is very bright

Typesafe’s Jonas Bonér said that the use of microservices, containers, Reactive streams and other new patterns have helped make software “more lightweight, loosely coupled and distributed.”

“ConductR’s design and architecture was designed to seamlessly fit into our customers’ environments to bring a more dynamic approach to managing these systems at scale,” said the CTO and co-founder.

It’s also been made clear that availability, resilience and responsiveness of the system have been prioritised during the development of this solution.

Over on cakesolutions, Tom Stockton explains that ConductR is “not designed to replace [Apache] Mesos, but rather to work with it as a highly available scheduler in the same way that Marathon does.”

According to Typesafe, ConductR offers the following advantages:

  • A RESTful API that works with automation tools such as Puppet, Chef and Ansible to automate resilient and flexible deployments
  • The ability to provide cluster-aware, proxy-based production releases
  • The ability to instantiate isolated and redundant application instances
  • A dynamic discovery of services (where the location is neither hard-coded into the Reactive, microservice-based systems, nor delivered as a configuration parameter)

Although an exact release date has not yet been announced, ConductR 1.0 is expected to be released in April 2015. A recent white paper that provides an overview of all benefits provided by ConductR, is available from Typesafe after registration.

Inline Feedbacks
View all comments