284 karma · joined April 12, 2025
Venture Capital is one of the greatest engines of growth, and fitting for the vast majority of early stage tech companies, it is interesting to see how changes in business economics may result in niche, differing capital structures. Eg. Companies which sell RL envs have vastly different economics than a food delivery app.
It was deprecated as the performance hurdle was significant.
This seems to utilize logical WAL replication and some form of dependency generation based on proxying a transaction's reads.
Managed Neon (Acquired by Databricks) also offers time travel [2].
One of the biggest challenges with this kind of solutions is handling ACID, OCC and/or HW failures correctly, Sometimes it requires an whole new language! [3]
[1] https://www.postgresql.org/docs/6.3/c0503.htm
[2] https://neon.com/docs/postgres/backup-restore/time-travel-as...
Modal significantly improves this. Highly recommend.
Not true as of last deployment.
> but zero technical detail
What additional technical detail would you be interested in?
> Also seems a couple orders of magnitude slower than what I’d expect even for a single core.
1) it's more than 2m/s on a MacBook AIR 2) Most of the latency is networking. This was a preliminary setup with a client / server over websockets where the book of 1m contracts combination of (strike, exp_date). Each insert only after a corresponding query has been returned (over the wire) from the previous insert. I can agree the eval isn't great; as in, the throughput is much higher.
> What exact transformations are being done
This is provided in the blog post.
Email me for details, pricing & installations, or your target use case, would love to talk. In addition, if you have any feedback.
ron at modolap dot com
As far as I can tell, incremental the library aims to solve the problem of partially hydrating a computation graph when source data is altered. This approach is similar to the one pursued by (well designed) build systems and is common in the FP world. [2] This has many use cases and is very cool.
In addition, in the sphere of incremental computation, there exists Differential Dataflow, Timely Dataflow (adjacent), and DBSP. Systems like Feldera are built on DBSP. Materialize is lead by some DD guys.
Personally, I am pursuing an orthogonal approach specifically for the problem of financial data and financial workloads, There exists huge, very important problems to solve! [1]
[2] Signals And Threads episode on the subject https://signalsandthreads.com/build-systems/
DST systems such as Antithesis can definitely help.
Just have superior CDC :)
> "how Modolap differs from just asking AI to use any other OLAP engine"
There presently exist two components, the OLAP query engine and the remote infrastructure service. The service enables systems like Codex (or developers as well) to manage datasets, maintain version control over queries, and offload the computational burden to dedicated machines. This is especially beneficial given the current trend of running agents inside micro-VMs.
In addition, it is designed with AI usage in mind. There is significant value in co-design. One could argue that models can use Polars or DuckDB just as well, and that there is no room for improvement, but I do not think this is true.
Polars seems to be the most prominent competitor in the Python DataFrame space, and DuckDB appears to pursue an approach similar to SQLite, but columnar.
I am personally working on a solution to a broader problem, which can also be viewed as an alternative to Pandas [2].
[1] https://wesmckinney.com/blog/apache-arrow-pandas-internals/