Hi Jay, Clearwater is massively scalable. All our components are designed from the ground up to scale out horizontally using simple, stateless load-balancing - so we don't store long-lived state on our individual nodes, but use (cloud-optimized) storage technologies such as Cassandra/Memcached.
For example, the Sprout cluster includes a redundant memcached cluster that stores client registration data (and other long-lived state). The SIP transactions are load balanced across the Sprout cluster, so there is no long-lived association between a client and a particular Sprout node. The failure of a Sprout node will affect any calls that are being set up, but will not impact any existing calls and registrations. You can see more about our architecture at http://www.projectclearwater.org/technical/clearwater-architecture/. Clearwater can also be geographically redundant - please see https://github.com/Metaswitch/clearwater-docs/wiki/Geographic-redundancy for more details of this. Ellie -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jaytirth Khairatkar Sent: 25 November 2014 05:18 To: [email protected] Subject: [Clearwater] Can Clearwater IMS nodes work in distributed mode? Hello, Is it possible to make multiple clearwater ims nodes work in a distributed way? Can they share load or handle failure of another node by taking over its activity? regards Jay _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
