[RFC] - Supporting infrastructure components for Wave

[gavinelder]

Background

Currently, Wave requires the use of Redis, SurrealDB & additional TinyKV to support a highly available deployment. This differs from the Seqera Platform which leverages Postgres & Redis which are available as managed services from major cloud providers for example Elasticache and RDS on AWS.

It would be nice if Wave could use a similar technology stack of that of Seqera Platform for enterprise deployments to reduce the complexity of deployments and increase the likelihood of adoption within regulated environments by reducing the barrier for approval.

Problem Statement

Enterprise customers deploying Wave on-premise face increased complexity and regulatory compliance requirements due to:

1. Additional infrastructure components requiring separate management
2. Self-hosted components such as SurrealDB & TinyKV that are not pre-approved for use within the business.

Impact

Deployment Challenges

• Extended deployment timelines due to additional security reviews
• Increased complexity in infrastructure certification process
• Need for specialized knowledge to manage non-standard / non-pre-approved components

Operational Overhead

• Higher ongoing management costs
• Additional monitoring and maintenance requirements
• Potential skills gap in operations teams

Business Impact

• Increased total cost of ownership
• Longer time-to-value for customers
• Potential barrier to adoption for enterprise customers
• risk of being denied approval to use wave.

Desired Outcome

Replace current self-hosted database solutions with managed services available from major cloud providers (AWS, Azure, GCP) to:

• Simplify deployment architecture
• Reduce operational overhead
• Align with existing enterprise infrastructure patterns
• Leverage familiar, well-documented services

Questions for Discussion

1. What are the specific features of SurrealDB that we rely on?
2. Which managed services could serve as viable alternatives?
3. What would be the migration path for existing installations?
4. Are there any performance implications to consider?
5. How would this affect our multi-cloud strategy?

Success Criteria

• Reduced deployment complexity
• Fewer components requiring self-management
• Maintained or improved performance
• Clear migration path for existing customers
• Support for major cloud providers

Additional Context

This request comes from an enterprise customer who already use managed services like AWS RDS and Elasticache for Seqera Platform deployments and would prefer a similar approach for Wave