Instance
An instance in Ascend.io is a specific setup of the platform within a designated subdomain. It serves as the parent for all resources, particularly your Environments, Workspaces, and Deployments.
Instances are powered by a number of underlying resources, including an Instance Store and Ascend-managed services.
Purpose and structure​
An instance acts as a dedicated operational environment that helps you manage data pipelines, resources, and configurations. It provides an isolated space where Projects and Workflows are contained, preventing interference between teams or business units.
Instances are essential for scaling, especially for large organizations that may require multiple instances for different regions, departments, or operational needs. Smaller or mid-sized organizations often use a single instance to meet all their requirements.
Key components​
-
Instance Store: Where all runtime metadata associated with an instance is stored, including builds, runs, and more.
-
Environments: Secure, isolated, and permissioned spaces for running Workspaces and Deployments.
-
Workspaces: Containerized runtimes where you can work directly on your Projects and Flows.
-
Deployments: Production-like runtimes for running your Projects and Flows on a regular basis.
-
Repositories: Connect your instance to Git Repositories, which are used to store your Project code.
-
Projects: Collections of code, configurations, and resources that define your data pipelines and flows. Projects are stored in Git repositories and can be worked on in Workspaces and deployed via Deployments.
Scalability​
While most organizations will be fine with a single instance, you can configure multiple instances to handle different operational needs, such as separating development teams, managing various product lines, or meeting regulatory requirements. Instances offer flexibility, enabling you to expand your use of the Ascend platform without reconfiguring existing setups.
Security and isolation​
Instances provide an added layer of security and operational isolation, ensuring that data and workflows remain within a specific instance. This setup prevents accidental data leaks or unauthorized access between instances. Instances support role-based access control (RBAC) and other security measures to maintain compliance and protect sensitive data.