SpacetimeDB: a short technical review
19 points by WilhelmVonWeiner
19 points by WilhelmVonWeiner
From my perspective SpacetimeDB looks a lot like Erlang/Elixir on BEAM. I'd rather use Erlang + NIFs.
It looked to me like the final form of an Entity-Component System (ECS), a database.
Though I guess if your code is data and your data is code all things will converge to the same concept?
(I'd also choose to use the BEAM :P).
One common mistake newcomers to the database space make is believing that you can win by having “the best performance”. I’ve never seen this in practice.
I will say the duckdb/clickhouse/umbra/cedardb space has certainly changed my perspective here a little from the days of mongodb's fsync stumbles.
It's an exciting time for performance-driven databases.
Jepsen review in 3, 2, 1...
(Probably not any time soon, tbqh, but it'd be a fun tear-down.)
I don't think there will be much to say, as the article says it's basically a lock around the in-memory storage