.. _architecture-offerings:

Architecture Offerings
----------------------

.. _21.1|VOSS-837:

VOSS Automate offers a range of deployment topologies.
The choice of a deployment topology should take
into consideration the advantages and disadvantages
of each as shown below.


* Single-node cluster (cluster-of-one/standalone)
* Single-node cluster (cluster-of-one/standalone) with VMWare HA
* Unified Node Cluster Topology

  * 2 Node with Web proxies
  * 4 Node with Web proxies
  * 6 Node with Web proxies
* Modular Cluster Topology (separate Application and Database nodes)

  * 3 Database nodes
  * 1 - 8 Application Nodes
  * Web Proxies
* Cloud deployments

  * Azure
  * Google Cloud Platform (GCP)
  * Support all Standalone, Unified and Modular cluster topologies
* MaaS (Management-as-a-Service)

  * VOSS hosted SaaS solution

+------------------+------------------------------+----------------------+
| Topology         | Pro's                        | Con's                |
+==================+==============================+======================+
|                  |   * Smallest hardware        |   * No DR            |
| Single-node [1]_ |     footprint                |   * Less throughput  |
|                  |                              |     than clusters    |
+------------------+------------------------------+----------------------+
| Single-node with |   * Smallest hardware        |   * Less throughput  |
| VMWare HA        |     footprint                |     than clusters    |
|                  |   * DR available             |                      |
+------------------+------------------------------+----------------------+
|                  |                              |   * More limitations |
| 3 Unified Node   |   * More throughput than     |     with DR          |
| Cluster          |     single-node              |     scenarios        |
|                  |                              |   * More hardware    |
|                  |                              |     than single-node |
+------------------+------------------------------+----------------------+
|                  |   * More DR scenarios        |                      |
| 4 Unified Node   |     supported                |   * More hardware    |
| Cluster          |   * More throughput than 3   |     than 3 Node      |
|                  |     Node                     |                      |
+------------------+------------------------------+----------------------+
|                  |   * Typically deployed for   |                      |
| 6 Unified Node   |     multi-data center        |   * Largest hardware |
| Cluster          |     deployments              |     footprint        |
|                  |   * Support Active/Standby   |                      |
+------------------+------------------------------+----------------------+
|                  |   * Increased processing     |                      |
|                  |     capacity utilization on  |                      |
|                  |     Application Nodes        |                      |
|                  |   * Horizontal scaling by    |                      |
|                  |     adding more Application  |                      |
|                  |     Nodes                    |                      |
|                  |   * Improved database        |                      |
| Modular Cluster  |     resilience with          |                      |
|                  |     dedicated nodes and      |                      |
|                  |     isolation from           |                      |
|                  |     application              |                      |
|                  |   * Improved database        |                      |
|                  |     performance by removing  |                      |
|                  |     application load from    |                      |
|                  |     the primary database     |                      |
+------------------+------------------------------+----------------------+
|                  |   * Leverage cloud tooling   |                      |
| Cloud Deployment |     like proxies (can use    |                      |
| (Azure, GCP)     |     instead of VOSS Web      |                      |
|                  |     Proxy)                   |                      |
+------------------+------------------------------+----------------------+
|                  |   * No hardware footprint or |                      |
| MaaS             |     infrastructure costs     |                      |
|                  |   * Fast setup               |                      |
+------------------+------------------------------+----------------------+



.. [1] This deployment should be used for test purposes only.