Servoy 2020 Documentation
Child pages
  • Servoy Cluster
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Current »

Terracotta deprecated DSO (Distributed Shared Objects)

Unfortunately Terracotta deprecated the technology that Servoy used to provide Servoy clustering (DSO). So clustering is only possible with older versions of Terracotta that still support DSO and only with Java 1.6 (not higher). That means that Servoy 8 (compiled for Java 1.7) will not work at all with Terracotta clustering. There is a case in the support system for switching to other clustering tech. Servoy 7.x should still work with Java 1.6 and now deprecated Terracotta DSO.

Until this gets addressed: if your solution can be split into multiple completely independent servers (each user being served by the same Servoy Server all the time) you can try doing that - so keeping multiple separate independent Servoy Servers. Each server in this case has it's own independent subset of data. But this means you have to have subsets of users that don't need to interact with data stored on another server (so no data broadcasting/locking/... needs - no real clustering needs).

 

Servoy provides built-in support for clustering. Servoy Cluster enables multiple Servoy Servers to be clustered as a single logical server, to facilitate larger number of connected clients and/or heavy workload to be distributed over multiple servers.

Servoy Application Servers in a Servoy Cluster share the same Servoy Repository and databases. The Servoy Cluster makes sure that:

  • Databroadcasting operates throughout the Servoy Cluster
  • Solution import operates throughout the Servoy Cluster

The Servoy Cluster allows for adding and removing Servoy Application Server instances to and from the Servoy Cluster, realtime, without having to restart the Servoy Cluster.

Coupled with Load Balancing Servers, the already scalable Servoy Application Server in combination with Servoy Cluster provides an even more scalable deployment platform for solutions, with fail-over built in, removing the dependency from a single machine. Servoy Cluster allows the adding and removing of additional Servoy Application Server instances to the cluster without having to restart the Servoy Cluster, making it very easy to respond to increased demand for solutions, without major investments due to having to replace existing hardware with more capable hardware.

Setting up and maintaining Servoy Cluster is straightforward and simple. For information how to setup Servoy Cluster, see Clustering Servers.

  • No labels