You can find the results of your search below. If you didn't find what you were looking for, you can create or edit the page named after your query with the appropriate button.
Design Goals:
2 Hitsow cost servers.
===== Design goals =====
* **Availability**: state-less front-end servers. A majority of ma... topology (subnets) modification and updates. High availability should be easy to achieve with standard and simpl
Overview:
2 Hitsority):
* **Reliability** (mainly through high availability)
* **Extendability** (being able to adapt to sp... *Extended**: (coming soon) multi-server with high availability database, very high performance, large network to
Hsqldb Back-end:
2 Hitsh brute performance, but is not suitable for high-availability cluster solutions or highly scalable services.
... e servers
* there is no support for active high-availability modes allowing automatic failover from one server
Architecture:
2 Hitsallowing for a wide range of scalability and high-availability solutions.
{{highlevelfrontback.png?nolink|High ... progress). It is highly recommended to build high-availability databases through clusters.
===== Thin client pr
Server internals:
1 Hits database is always up and running (cluster, high availability solutions...).
May the front-end not be able to
Server configuration:
1 Hitsy is to put all data is the database when in high-availability mode (to be described later).
===== Configuratio
Frequently Asked Questions:
1 Hits persistence on the server side which raises some availability issues. Such servers should also be aware of deni
