Solutions are deployed with Servoy either in a client-server setup or locally installed. Over 98% of all deployments with Servoy use client/server deployment. Locally installed applications use the Servoy Runtime Client,
Servoy supports in basis 2 ways to deploy solutions:
Client Server deployment involves a centralised server which runs Servoy Server from which any of the Servoy clients can be launched. Although technically the same Client Server deployment can be implemented in three different ways:
On premises deployment typically means that the application server is located on the same premises as the users of an application.
Optimal configuration:
Servoy wil run fine without the optimal configuration but with the configuration above there will be less cpu usage, less memory usage, better performance and less potential network issues
Servoy can also be deployed using SaaS. There are a couple of ways to do this:
Servoy supports the main three SaaS paradigms:
For SaaS deployment the server installation and management is identical to a normal installation.
Servoy can be deployed in most cloud computing environments. Essentially all you need is a database (this can be a third party or the included PostgreSQL database) and the possibility to run a Java process (Java 5 or higher, Java 6 recommended).
Servoy Server can then be installed on the server, either with the GUI installation (if a GUI is available) or command line. It is also possible to copy a directory of Servoy from one server to another. As there are some batch scripts it is recommended to only make copies between similar operating systems. Additionally if the included PostgreSQL database is used the binaries are not cross platform.
To increase availability or performance it is possible to use Servoy Cluster and combine multiple servers.
Servoy can be deployed in two ways for stand alone usage.
Client/Server
In this case a server is installed locally and a Smart or web client is deployed from that server to the local user
Runtime
Using the Servoy Runtime builder a runtime is generated that contains a doubleclickable executable. No server installation is necessary and the folder in which the runtime resides is portable (it can be moved between different machines as long as they have the same host operating system)
Pro's & Con's