SpacetimeDB
Ranked 10 of 22 databases by recommenders
Fans praise its speed and its blend of actor-style processing with relational data for persistent games. Critics say benchmarks are misleading and it does not clearly match CockroachDB's failure tolerance.
Fans praise its speed and its blend of actor-style processing with relational data for persistent games. Critics say benchmarks are misleading and it does not clearly match CockroachDB's failure tolerance.
43 people gave an opinion
- recommend it
- 26
- criticize it
- 17
- approval share
- 60%
Recommended in 6 of 13 months
- November 2025: not recommended
- December 2025: not recommended
- January 2026: not recommended
- February 2026: recommended
- March 2026: recommended
- April 2026: recommended
- May 2026: not recommended
- June 2026: recommended
- July 2026: not recommended
- August 2026: recommended
- September 2026: recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 26 people recommend itNeeds 10 or more, met.
- 1.5 recommenders for every criticNeeds 2 to 1 or better, not met.
- Recommended in 6 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Very fast performance
“As someone who has been using alot of spacetime for side projects, I am continually impressed with the speed at which it operates.”
Comment from 4 Sep 2026 in “Ok, but does it scale?” “Using the same module written in Rust, we can do even better on the same machine, 165k+ TPS.”
Comment from 24 Feb 2026 in “SpacetimeDB 2.0 [video]” “we're so far out ahead of typical database performance for most OLTP workloads”
Comment from 21 Aug 2026 in “SpacetimeDB: A Short Technical Review” - Comment from 21 Aug 2026 in “SpacetimeDB: A Short Technical Review”
Good fit for persistent game state
“We feel very comfortable that it's the most performant backend for persistent games though.”
Comment from 4 Sep 2026 in “Ok, but does it scale?” “This looks very promising. There's a need for persisting game state in a central place”
Comment from 25 Feb 2026 in “SpacetimeDB ThreeJS Support” “SpacetimeDB has worked very well in my game so far.”
Comment from 2 Mar 2026 in “SpacetimeDB ThreeJS Support” Liked by developers overall
“I think the product is great and I do really like it”
Comment from 26 Feb 2026 in “An honest analysis of SpacetimeDB 2.0's insane benchmark results” “SpacetimeDB has worked very well in my game so far.”
Comment from 2 Mar 2026 in “SpacetimeDB ThreeJS Support” “I like the core idea quite a bit”
Comment from 21 Aug 2026 in “SpacetimeDB: A Short Technical Review” - Comment from 4 Sep 2026 in “Ok, but does it scale?”
What people warn about
Each mark is one comment
Benchmarks seen as misleading
“I'm not sure that the comparison between CRDB is a good one.”
Comment from 4 Sep 2026 in “Ok, but does it scale?” “It felt a little dishonest due to using different clients, protocols, concurrency, etc in the benchmarks”
Comment from 25 Feb 2026 in “An honest analysis of SpacetimeDB 2.0's insane benchmark results” “SpacetimeDBs “benchmarks” might be the most egregious, blatantly misleading benchmark I’ve ever seen”
Comment from 26 Jun 2026 in “Lies, Damn Lies and Database Benchmarks” - Comment from 4 Sep 2026 in “Ok, but does it scale?”
Risk of data loss on crash
“I don't see anything that indicates how spacetime solves the core problem CRDB does, which is guaranteeing that single node failures can be tolerated with zero data loss or loss of availability”
Comment from 4 Sep 2026 in “Ok, but does it scale?” “They are yolo mode by default with periodic fsync and a big mutex around every reducer”
Comment from 4 Sep 2026 in “Ok, but does it scale?” “If rolling back a few minutes is tolerable in exceptional scenarios then I disagree.”
Comment from 4 Sep 2026 in “Ok, but does it scale?” Global lock limits concurrency
“I concede that we do have a big lock. But that is only because we did the alternative first and it performed worse”
Comment from 4 Sep 2026 in “Ok, but does it scale?” “They are yolo mode by default with periodic fsync and a big mutex around every reducer”
Comment from 4 Sep 2026 in “Ok, but does it scale?” “I don't think this can compare with TigerBeetle just because both are single threaded”
Comment from 24 Aug 2026 in “SpacetimeDB: A Short Technical Review” - Comment from 20 Aug 2026 in “SpacetimeDB: A Short Technical Review”
Lock-in and restrictive license
“i am reluctant to be tied into a platform that my project cannot work without”
Comment from 1 Mar 2026 in “SpacetimeDB ThreeJS Support” “Not an opened source license, they allow to use only 1 production server”
Comment from 24 Feb 2026 in “SpacetimeDB 2.0 [video]”
Other databases people recommend
The four most recommended other databases, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| PostgreSQL | 816 | 233 | 78% | 13 | 10 yrs42 owners | Approved |
| MySQL | 124 | 107 | 54% | 12 | — | — |
| Microsoft SQL Server | 73 | 59 | 55% | 12 | 20 yrs6 owners | — |
| Microsoft Access | 62 | 39 | 61% | 12 | — | — |
| SpacetimeDBThis page | 26 | 17 | 60% | 6 | — | — |
What people said
40 of the 60 comments that mention it, newest first. Each links to the original comment.
“achieves amazing performance by making everything a stored procedure”
“Also look at single core focused systems like spacetimedb, sometimes if a workload is not embarrassingly parallelizable”
“it blends the processing model of actors and the data model of relational databases really neatly”
“SpacetimeDB Cloud has the same exact behavior as CRDB in terms of tolerating single node failure and loss of availability”
“I don't see anything that indicates how spacetime solves the core problem CRDB does, which is guaranteeing that single node failures can be tolerated with zero data loss or loss of availability”
“I concede that we do have a big lock. But that is only because we did the alternative first and it performed worse”
“They are yolo mode by default with periodic fsync and a big mutex around every reducer”
“I'm not sure that the comparison between CRDB is a good one.”
“If rolling back a few minutes is tolerable in exceptional scenarios then I disagree.”
“As someone who has been using alot of spacetime for side projects, I am continually impressed with the speed at which it operates.”
“We feel very comfortable that it's the most performant backend for persistent games though.”
“the benchmarks make assumptions about your stack doesn't sit right with me”
“I'm curious to try out Spacetime in a project now.”
“It's super cool tech imo.”
“I don't think this can compare with TigerBeetle just because both are single threaded”
“don't really trust how new it is nor all the weird marketing behind it”
“it does have a RwLock, but that is by design and produces better results than the alternative.”
“I like the core idea quite a bit”
“we're so far out ahead of typical database performance for most OLTP workloads”
“it's simply faster for almost all workloads”
“single threaded execution is optimal for performance here”
“We do not need to trust them, we employ a system like Ethereum's gas limits to prevent infinite loops.”
“For some reason they apparently lock things while "reducer"s are running.”
“I'm somewhat impressed by the results, it's not exactly surprising to me when you make the trade-offs they're making”
“I had a lot of criticisms of what he was making and the way it was being made”
“SpacetimeDBs “benchmarks” might be the most egregious, blatantly misleading benchmark I’ve ever seen”
“Some of their work utilizing Rust was interesting.”
“Specifically targeting your use case with high fps.”
“I worked in SpacetimeDB and I proudly say is half-way”
“SpacetimeDB has worked very well in my game so far.”
“It was surprisingly easy to build the standalone demo but the full integration obviously is not as straightforward.”
“But I am still a bit skeptical at how scalable this is.”
“i am reluctant to be tied into a platform that my project cannot work without”
“I think the product is great and I do really like it”
“This looks very promising. There's a need for persisting game state in a central place”
“the server stays authoritative and the client just renders and interpolates”
“It felt a little dishonest due to using different clients, protocols, concurrency, etc in the benchmarks”
“I'm realizing what they are claiming to do if true will make it much faster to ship.”
“Using the same module written in Rust, we can do even better on the same machine, 165k+ TPS.”
“Not an opened source license, they allow to use only 1 production server”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.