Yes sure, dev containers inside each project, that way the entire environment (debugger, all ide plugins for linting etc) are standard across all devs and the coding environment matches prod exactly
Can you get away without exposing it to the internet? Firewall it off altogether, or just open the address of a specific machine that needs access to it?
Hi, I've been loking something like this!
Any of your custumer has success story migrating off bigquery to your platform?
And how do you compare to motherduck? (Looks like you built some of ypur stack on top of duckdb)
Yes, we've had many bigquery / snowflake converts. The reality is, most companies don't have 100tb of data (which is what those platforms are optimized for). Motherduck has a good post[0] on this:
> There were many thousands of customers who paid less than $10 a month for storage, which is half a terabyte. Among customers who were using the service heavily, the median data storage size was much less than 100 GB.
I'm a fan of what motherduck is doing. We're building something different (opinionated, instant data stack), but yes, we both use duckdb under the hood.
Anyone have tried comparing with Qwen VL based model?
I heard good things about its performance on ocr compared to other self hostable model, but haven't really tried benchmarking its performance
Our initial approach was to implement periodic full table re-syncing. We're starting to work on CDC with logical replication for incremental syncing. Here is our roadmap https://github.com/BemiHQ/BemiDB#future-roadmap
reply