Duckdb

[joeblew999]

In https://github.com/blinkinglight/gobeego/blob/main/pkg/rwdb/rwdb.go

I tried a swap out to use go duckdb . This allows many more options .. for deployment.

Works great .

Local , remote, etc .

Was thinking about a way to support both , but not sure you want this .

[joeblew999]

I started using ducklake . It’s duckdb extension .

https://ducklake.select/

It allows multi writers . SQL holds the catalog and s3 holds the data .

It’s the sink in the CQRS pipeline. The materialised views . It’s multi version due to the nature of how ducklake works , allowing a full audit trail and time travel .

Ducklake has a change feed system too , which works really well with S3 and NATS. Minio fires events to nats and allowing the change feed to be processed