citguru

Lol, love it

True, but still a big issue today

Debbie, probably needs more email training

Not just that. You could ask any more complex questions. Thats just an easy example

Actually while similar to Jev and uses the popularized architecture by Jev, Kairos uses an underlying model called Grayson trained by Finic but for Fraud. You can check it out - https://finic.ai/

There will always be projects that share the same name. You can do quick search on Github: https://github.com/search?q=kairos&type=repositories. However it does not change the significance of what each project is building and the problem they sought to solve.

Seems really cool. I am skeptical about using external Whatsapp client due to hacks

Nothing is built yet. Before I spend time building it, I want the idea roasted.

LaunchPort: launch your side project and get real customers without incorporating first. You'd keep the code, IP, and customers. Infra, payments, sales/marketing and legal handled for you; you "graduate" into your own company whenever you're ready.

Do you get what this does? Would you actually sign up? What would stop you?

Landing page for context: https://launchport.lovable.app/

I needed to back up terabytes of Postgres RDS data to R2 without intermediate local dumps or AWS egress fees, I could not find any ideal solution, so I built this.

Hi,

DuckLake is great for the lakehouse layer and it's what we use in production. But there's a gap and thats what I'm trying to address with OpenDuck. DuckLake do solve concurrent access at the lakehouse/catalog level and table management.

But the moment you need to fall back to DuckDB's own compute for things DuckLake doesn't support yet, you're back to a single .duckdb file with exclusive locking. One process writes, nobody else reads.

OpenDuck sits at a different layer. It intercepts DuckDB's file I/O and replaces it with a differential storage engine which is append-only layers with snapshot isolation.

The project is still fairly new and not close to production tbh.

I'd actually recommend the simplest option: just write them to Parquet on S3 and query with plain DuckDB. Or you could use Ducklake - https://ducklake.select/

Thanks for this, really enjoyed reading this and helps validate some of my personal thoughts

This is an attempt to replicate MotherDucks differential storage and implement hybrid query execution on DuckDB

Already started porting some of the services, but alot are tightly coupled with AWS services

10 hours is too much time. Time is money, we deal with time sensitive business. If people are not able to process transactions how are their users able to do their daily activities. Money was definitely lost once the Finance team analyse the situation

Developer Plan