Integration / Apache Pulsar Interview questions
What is the difference between SaaS and On-Premises Controller deployments?
Both deployment modes run the same core Controller software, but they differ in who operates the infrastructure and what that implies for maintenance, scaling, and data residency.
| SaaS Controller | On-Premises Controller |
| Hosted and operated by Cisco/Splunk. | Installed and operated inside the customer's own infrastructure. |
| Upgrades and scaling handled by the vendor. | Upgrades and capacity planning are the customer's responsibility. |
| Data leaves the customer's network to reach the Controller. | Data can stay entirely within the customer's own network boundary. |
| Faster initial setup, lower operational overhead. | More control over configuration, patch timing, and compliance posture. |
The choice usually comes down to regulatory or data-residency requirements: organizations in heavily regulated industries, or with strict rules about where telemetry can be transmitted, often choose on-premises specifically to keep monitoring data inside their own network, even though it means owning the operational burden themselves.
Who is responsible for Controller upgrades in the SaaS deployment model?
Why might an organization choose an on-premises Controller?
More Related questions...
