New content

app/views/conductr/index.scala.html

@@ -6,12 +6,20 @@
         <div class="row">
             <div class="small-12 medium-7 large-8 columns">
                 <h1>Today’s demands on Operations are simply not met by yesterday’s software architectures and technologies</h1>
-                <p>Reactive application development becoming mainstream is leading to demands on Operations that are simply not met by yesterday’s software architectures and technologies.</p>
-                <p>The demands placed on systems are ruthless nowadays. Starting with global expansion in mobile technology and continuing now with IoT, Operations deals with exponentially greater loads; yet for all their efforts, services provided by airlines, banks, retailers and telecommunications providers are still perceived to be sluggish.</p>
-                <p>ConductR is a management tool for Operations to deploy and control Reactive applications running in a cluster. Supplementing existing tools that focus on more traditional, monolithic application architectures, ConductR is built specifically for distributed Reactive applications, reflecting that Operations requires a different approach to both the tools and methodologies they use.</p>
-                <p>ConductR is designed to run with the Typesafe Reactive Platform and provides a RESTful API to integrate with existing tools (e.g. Amazon EC2, Docker, Puppet, Chef, Ansible and Akka Cluster) to provide immutable, DevOps-friendly deployments.</p>
+                <p>ConductR is a solution for managing Typesafe Reactive Platform applications across a cluster of machines. ConductR is reactive from the ground up thus enabling operations to provide the resiliency required to unleash the full benefits of the Typesafe Reactive Platform in their organization.</p>
+
+                <p>ConductR moves beyond simply running multiple instances of the services that are your applications. 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.</p>
+
+                <p>ConductR’s design was influenced by Mesos by adopting its notion of resource requests and offers, and support for Docker containers for example. ConductR runs stand-alone and is also planned to be available as a Mesos framework later this year. ConductR is also a refreshing alternative to using Apache ZooKeeper for service discovery in your applications and services.</p>
 
                 <img src="@routes.Assets.at("images/svg/conductR-and-reactive-system-architecture.svg")">
+
+                <p>ConductR is light-weight and highly resilient. Each node runs the ConductR process, a proxy (HAproxy) and conductr-haproxy; a reactive configuration process. This combination enables any node in the cluster to proxy requests for any service endpoint of the cluster leaving no single point of failure. ConductR leverages Akka clustering, data replication, FSM (Finite State Machine), reactive streams, CRDTs and more to provide the must have features such as consolidated logging, service discovery and rolling upgrades.</p>
+
+                <p>Our goal is that ConductR becomes known to the operator in a similar way to how Play is now known to the developer: a productive and joyful experience. Enjoy!</p>
+
+                <p>Warm regards,
+                <br/>The ConductR Team</p>
             </div>
             <div class="medium-5 large-4 hide-for-small-only columns">
                 <div id="inPageTOC" class="in-page-toc toc-wrapper">