Hybrid SaaS
Introduction
This document outlines the architecture and operational framework of the Hybrid (SaaS) deployment model for Observo. It explains how the Manager and Sites operate within this setup, detailing the flow of data and the benefits customers can expect. Please follow the guide on Deployment of Observo Site for this model.

Manager as the Control Plane
Centralized Control in Observo Cloud
The Manager serves as the orchestrating control plane within Observo Cloud. It efficiently manages a widespread network of sites across a variety of customers, each operating within their distinct Virtual Private Clouds (VPCs).
Streamlined Customer Deployment
Customer deployment is simplified. Customers only need to install the Observo Site software. After installation, the Site communicates consistently with the centrally hosted Manager via an Agent installed at each site.
Data Exchange Mechanisms
Limited Scope of Data Exchange
The data exchange between the Sites and the Manager is limited to control plane data, metrics, and logs. This restriction ensures security and efficiency and is further explained in preceding sections.
Alignment with Private Cloud Models
The hybrid deployment model aligns with traditional private cloud setups. The control and data flow models remain consistent, maintaining a uniform management approach.
Distinctions of the Hybrid Model
Manager Placement within Observo
A key distinction of the hybrid model is that the Manager is hosted within the Observo Cloud. This allows for centralized management of all operations.
Sites Deployed in Customer VPCs
In contrast, Observo Sites are deployed within individual customer VPCs, creating a distributed network of local nodes.
Confined Data Flow
Localized Data Handling
Data flow is confined within each customer's VPC. Sites ingest data from sources within their VPC and write data to reachable destinations within the same VPC. This approach enhances security and performance.
Enhanced Security and Performance
By ensuring data does not traverse beyond the secure VPC boundaries, security is significantly enhanced. This localized data flow also optimizes performance by reducing latency and minimizing potential points of failure.
Benefits of a Hybrid Approach
Centralized Management with Local Processing
The hybrid (SaaS) deployment model combines centralized management by the Manager with the processing power of localized Sites, ensuring a seamless and efficient operational framework.
Scalability and Robustness
This model supports scalability and robustness. Centralized oversight ensures uniform policy enforcement and system updates, while localized Sites guarantee optimal data processing and integrity.
Summary
Observo Cloud manages the Manager cluster within its infrastructure.
Site deployment occurs within customer VPCs.
Observo Cloud efficiently handles multiple Sites across customer VPCs.
Manager endpoints must be accessible from customer VPCs where Sites are deployed.
The Manager exclusively functions as the control plane and does not require access to customer data sources or destinations.
Site deployment is streamlined, using helm charts and typically taking 15 minutes to install and connect to Observo Cloud. Once deployed, Sites automatically establish communication with Observo Cloud.
The Site deployment offers flexibility, allowing installation on either an existing Kubernetes cluster or a new one. Additionally, it can be deployed on an EC2 instance or any virtual machine (VM) that supports a flavor of Kubernetes cluster.
Data Ingestion
Each Site ingests data directly from defined sources within the customer's VPC.
It can write data to one or more destinations configured by the customer, enabling flexible data routing and processing. Destinations must be reachable from the VPC where the Site is deployed.
External Dependencies
Site installation does not rely on external dependencies. It can be installed on a valid Kubernetes cluster or even on a single node or VM, provided a K8s or micro K8s cluster is available.
Last updated
Was this helpful?

