typescript is wildly successful because it not a special js runtime and produces js code that can work with existing libraries 100% of the time

but then there will be differences in behavior that impacts how you thought your program ran.. things still wont work at the end lots of libraries need to be re-written in mojo. and that's ok.

its not going to just work if you try to use your existing python program.. after a lot of new extra work the existing programs will start working and they might even have 100% coverage in terms of python functionality on paper..

you mean duck

👋

just point FalServerlessRunner to your local dbt directory and it takes care of the rest. syncs the project to the cloud, prepares an environment if necessary, runs the dbt command and releases cloud resources

this is coming along nicely, bonus: also running a small `dbt run` with each event and only storing the transformed table

You can follow along here:

https://github.com/fal-ai/fal-events

The beautiful part of this is that the simplest version of this implementation is really simple and good enough for a lot people

Most certainly this will become a problem. I dont expect duckdb to handle a large amount of writes. All the events will be stored in a single duckdb file, that wont scale forever at that point we can swap up storage with open source delta lake (delta-rs) or iceberg

I expect this project to grow as our company grows. First we'll be sending all events directly to a duckdb instance and everything will be stored there

This will be a reference implementation to how do build such a system using fal-serverless

Previously we were using posthog and snowflake. We don't have a lot data but still snowflake was charging us 1k a month