Hi, thanks for shipping the AWS Lambda distributed rendering support.
Would you consider adding an official Google Cloud adapter as well, either for Cloud Run, Cloud Run Jobs, or Firebase Functions 2nd gen?
From the discussion in #677, it sounds like the distributed rendering primitives are already provider-agnostic and the AWS Lambda package is mainly the deployment/orchestration/storage adapter. A Google Cloud adapter could follow a similar model:
- GCS / Firebase Storage instead of S3
- Cloud Run / Firebase Functions instead of Lambda
- Cloud Run Jobs, Cloud Tasks, or Workflows for chunk fan-out
- Same
plan, renderChunk, and assemble primitives from @hyperframes/producer/distributed
This would be useful for teams already running their backend and storage on Google Cloud who want distributed HyperFrames rendering without adding AWS infrastructure.
A minimal first version could just document the recommended architecture and expose reusable adapter helpers for GCS transport and Cloud Run/Firebase handler shapes.
Hi, thanks for shipping the AWS Lambda distributed rendering support.
Would you consider adding an official Google Cloud adapter as well, either for Cloud Run, Cloud Run Jobs, or Firebase Functions 2nd gen?
From the discussion in #677, it sounds like the distributed rendering primitives are already provider-agnostic and the AWS Lambda package is mainly the deployment/orchestration/storage adapter. A Google Cloud adapter could follow a similar model:
plan,renderChunk, andassembleprimitives from@hyperframes/producer/distributedThis would be useful for teams already running their backend and storage on Google Cloud who want distributed HyperFrames rendering without adding AWS infrastructure.
A minimal first version could just document the recommended architecture and expose reusable adapter helpers for GCS transport and Cloud Run/Firebase handler shapes.