Starburst

1. Pre-Implementation Planning:

   • Identify and Prioritize Data: Determine which data needs to be migrated, focusing on core data and excluding unnecessary data. This step involves creating a data inventory to prioritize the migration process.

   • Explore, Inventory, and Back Up Data: Validate the quality, quantity, and relevance of the data. Back up or create snapshots as needed and finalize the target environment for the data.

2. Setting Up Starburst Enterprise:

   • Configure Starburst Enterprise in the AWS Cloud: Set up Starburst Enterprise in a managed Amazon EKS cluster while data is being catalogued. This involves deploying Starburst using Kubernetes and Helm charts.

   • Connect Starburst to Data Sources: After setting up Starburst Enterprise, connect it to the data sources. Starburst reads data directly from the source as a SQL query.

3. Data Migration:

   • Build and Run ETL Pipelines: Begin the data migration process using either Starburst or a third-party ETL application. This step can occur concurrently with regular business operations.

   • Validate the Data: After migration, validate the data to ensure all required data has been moved and is intact.

Roles Involved

• Cloud Administrator: Responsible for making cloud resources available and managing the Starburst application.

• Data Engineer: Handles the migration of legacy data to the cloud and builds semantic views to support analytics.

• Solution/System Owner: Oversees the overall solution implementation.

1. Mode Analytics Integration: Mode Analytics, which integrates with Starburst, allows for complete customization using HTML, CSS, JavaScript, APIs, and custom themes to tailor internal data tools to team needs.

2. CloudFormation Templates: Starburst Enterprise can be customized using CloudFormation templates. Configuration packages for the coordinator, workers, and catalogs can be used to append or override the default SEP configuration.

3. Low-Code Solutions: Starburst has introduced low-code solutions for building, sharing, and curating data products, making it easier to customize data consumption processes.

1. Starburst Galaxy: Offers a pay-as-you-go pricing model with no upfront commitment. Costs are based on the uptime and usage of clusters, with pricing varying by execution mode, cloud platform, and region.

2. Starburst Enterprise: Additional costs may include infrastructure, networking, data security, and governance expertise.

3. Support Charges: Starburst offers 24/7 support with varying response times based on the severity of the issue. Support is included in the subscription plans.

1. Training Series: Starburst offers a 5-part training series on designing high-performance data lake table structures and exploring Apache Iceberg features.

2. Starburst Academy: Provides courses for both beginners and experienced data professionals.

3. Support Policy: Support is available 24/7 for urgent issues, with response times varying based on severity. Customers can designate up to three key contacts for support requests.

1. End-to-End Encryption: Starburst includes end-to-end encryption, different authentication types, fine-grained access control, and detailed security auditing.

2. Data Protection: No secrets such as usernames or passwords are stored on disk, and files are not accessible from outside the running EC2 instances.

3. Third-Party Integrations: Starburst integrates with third-party security providers like Immuta for dynamic, scalable protection.

1. Quarterly Releases: Starburst follows a quarterly release process for the Long Term Support (LTS) version and regularly patches these versions with security and bug fixes.

2. Communication: New releases and patches are communicated to customers via the account team and are publicly available on the documentation.

1. Customer Control: All data sources are completely under the customer's control, and no data is stored in Starburst Enterprise Platform (SEP).

2. Encryption: Data caching and transfer functions are managed within the customer's systems, and encryption (TLS) can be configured for all data in transit.

1. Elastic Scaling: Starburst allows for elastic scaling of compute resources to meet demand, enabling organizations to scale up or down as needed.

2. Pricing Model: Starburst Galaxy's pricing model is based on the number of worker nodes in a cluster and the total uptime, allowing for flexible scaling.

1. User Agreement: Access to EventsX is governed by its User Terms, which form a legally binding contract once accepted.

2. Automatic Renewal: Subscriptions typically renew automatically unless canceled before the renewal date.

3. Cancellation Rights: Clients can cancel by providing notice before the next billing cycle; otherwise, charges for the next term may apply.

4. Refunds: Refunds are generally not provided for unused portions of a subscription unless required by law.

5. Termination by EventsX: The company reserves the right to suspend or terminate accounts for breach of terms, misuse, or non-payment.

6. Enterprise Contracts: Renewal and cancellation terms are negotiable and often include service-level agreements (SLAs).

7. Data Handling Post-Cancellation: Clients can request data export before termination; EventsX may delete data after account closure.

1. SOC 2 Type 2 and ISO/IEC 27001: Starburst meets several compliance standards, including SOC 2 Type 2 and ISO/IEC 27001 certifications.

2. Annual Risk Assessments: The company conducts annual risk assessments and manages a risk register to ensure appropriate application of resources to minimize any negative impact.