Typesafe Launches ConductR to Simplify Operations for Reactive Systems

Date 2015/3/17 9:54:49 | Topic: Product News

Typesafe, provider of the world's leading Reactive platform and the company behind Play Framework, Akka, and Scala, today announced Typesafe ConductR -- the first system designed specifically for IT operations teams to deploy and manage Typesafe Reactive Platform applications across multiple servers in clusters.
Reactive applications are designed to be responsive, resilient and elastic at scale in the face of heavy traffic or spontaneous failures. Consequently, they are highly distributed by design (written to run across multiple servers). But operators today face many challenges in managing clusters of Reactive applications. Existing infrastructure automation tools, while useful, have not been designed with the demands of modern distributed applications in mind. Operators are forced either to create and expensively maintain their own custom, home-grown solutions or cobble together a patchwork of disparate proprietary and open source tools. Practical service level agreements (SLAs) are almost impossible in these cobbled-together environments.

Typesafe ConductR is designed to address the challenges of deploying and managing Reactive applications in distributed environments by expecting failure while prioritizing system responsiveness and uptime for users. ConductR enables operations to more easily deploy and manage Typesafe Reactive Platform applications on clusters, and to exploit the benefits of Reactive systems.

ConductR helps operations with coverage for an entire application cluster, prioritizing availability, resilience and long-term maintenance of a Reactive system. The benefits include:
* Automate resilient and elastic deployments: ConductR provides a convenient RESTful API to work with your existing provisioning automation tools like Puppet, Chef, Ansible and others. 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.
* Deploy cluster-ready, proxy-based production releases: ConductR lets developers bundle application and configuration, while keeping configuration parameters isolated. When operations deploys application/service bundles, ConductR distributes them across the cluster where resources are known to be available. ConductR uses asynchronous libraries with back-pressure detection mechanisms in order to make the most effective use of the resources it has available, using proven technologies to proxy requests and locate services.
* Instantiate isolated and redundant application instances: ConductR lets users scale bundles up and down, as well as add and remove nodes on demand without interrupting the availability and responsiveness of the system as a whole. ConductR's distinctive approach ensures that new application bundles are quickly instantiated around the cluster, letting any node can take on any responsibility. In the case of failure, it remains isolated within each bundle, thereby ensuring that parts of the system can fail and recover singularly without compromising the system as a whole.
* Dynamic discovery for "anywhere" services: Reactive, microservices-based systems are loosely coupled, so service location information is not hard-coded into the application or provided as a configuration parameter. Because a service could be running anywhere, ConductR uses dynamic service discovery to find a service name and provide an address, which will live for enough time to carry out the operation and ensure that all critical services are responsive.



This article comes from Software Development Tools
http://www.softdevtools.com

The URL for this story is:
http://www.softdevtools.com/modules/news/article.php?storyid=3642