data lifecycles • Different access profiles • Expect different SLAs • Different backup policies • Different versions Operations • Maintenance windows are difficult • Fair use is hard, to impossible • Upgrades affect all tenants • Data isolation is not complete • KibanaS VS
(by volume, tenant, use case, access profile) ‒ When one tenant gets its own cluster, the others will want one too • You now have multiple clusters to manage ‒ Different Elasticsearch versions ‒ Different support SLAs ‒ Different HW? Same HW? How do you isolate resources? ‒ What about backups? ‒ What about security? ‒ How do you even track and monitor all of this? Architectural decisions informed by business need
in your private cloud … or wherever you want Leverages the same technology used in Elastic Cloud Automates frequent tasks such as snapshot/restore, upgrade and scale
As a backing service for PaaS / SaaS ‒ Service Brokers for CloudFoundry and OpenShift ‒ Cluster per customer in a SaaS app • Easily create a cluster per user / tenant • Maintain isolation between users and tenants Discovering new uses inside of your business