Volterra SaaS service is comprised of three main components and this terminology may be used in the rest of the concepts section.
- Centralized Control and Management Plane - this component runs in a combination of Volterra’s global infrastructure as well as public cloud providers like AWS, Azure, and GCP. This is the main component and the portal (also called VoltConsole) of the SaaS service that users interface with using APIs or their browser. This component provides a multi-tenanted solution to manage the lifecycle of the infrastructure, applications, services, and observability. Customers interface to this centralized SaaS portal through APIs or using their browser.
- Site - This could be a customer location like AWS, Azure, private cloud, or an edge site. In order to run Volterra service (eg. VoltMesh or VoltStack), the site needs to be deployed with one or more instances of Volterra Node, a software appliance that is managed from VoltConsole. This site is where customer applications and Volterra services are running. Theoretically, there could be more than one site in a customer location and these sites may optionally connect to each other directly using site-to-site tunnels. These customer sites automatically connect to the Volterra’s global network by setting up redundant IPSEC or SSL tunnels to the Regional Edge sites.
- Regional Edges (RE) in Volterra global infrastructure - Volterra points of presence with their own highly meshed backbone are used to provide customer services (eg. VoltMesh or VoltStack). These points of presence are also used to connect multiple customer Sites to each other. These REs can also be used to expose customer services to the public internet. These RE sites can also be used to run customer applications so that they are closer to end consumers on public Internet or their distributed application locations.