Architecture Offerings

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

Single-node 1

  • Smallest hardware footprint

  • No DR

  • Less throughput than clusters

Single-node with VMWare HA

  • Smallest hardware footprint

  • DR available

  • Less throughput than clusters

3 Unified Node Cluster

  • More throughput than single-node

  • More limitations with DR scenarios

  • More hardware than single-node

4 Unified Node Cluster

  • More DR scenarios supported

  • More throughput than 3 Node

  • More hardware than 3 Node

6 Unified Node Cluster

  • Typically deployed for multi-data center deployments

  • Support Active/Standby

  • Largest hardware footprint

Modular Cluster

  • Increased processing capacity utilization on Application Nodes

  • Horizontal scaling by adding more Application Nodes

  • Improved database resilience with dedicated nodes and isolation from application

  • Improved database performance by removing application load from the primary database

Cloud Deployment (Azure, GCP)

  • Leverage cloud tooling like proxies (can use instead of VOSS Web Proxy)

MaaS

  • No hardware footprint or infrastructure costs

  • Fast setup

1

This deployment should be used for test purposes only.