Workspaces Implementation

Workspaces leverage SingleStoreDB’s unique architecture and data durability guarantees to launch isolated compute pools for running discrete customer workloads.

Each workspace is a part of a Workspace Group, which allows for the configuration and management of access, updates, and data sharing. Databases can be attached or detached from any workspace within a workspace group. Each group can contain up to five workspaces, and each database can have one R/W (read and write) and many R/O (read only) attachments.

Each workspace group is deployed in a cloud provider and region. An organization can have many workspace groups deployed across multiple cloud providers and regions.

workspace-groups.png

Workspace Groups Updates

Scheduled updates are applied to each workspace group based on the update window assigned. Updates are applied to all workspaces in a group simultaneously during the scheduled window.

Workloads that receive updates independently should be run in separate workspace groups to ensure independent update schedules. For example development and production workspaces should run in separate groups. Thereby ensuring updates are applied to development before production.

Migrating Existing Clusters to Workspaces

Existing customers using clusters can migrate to workspaces by contacting SingleStoreDB Support to plan and implement the move.

Note

All features and capabilities available for clusters are applicable in workspaces. Management of users, groups, roles, permissions, firewall, resource governor pools, and global system variables settings can be done only at the workspace group level.