SpacetimeDB

> I asked was about querying data without ever using a SQL language, like tapping directly into the data. I agree (making https://tablam.org to try a fix & working on https://github.com/clockworklabs/SpacetimeDB in the SQL conformance). Before I think SQL was bad. *Now I'm certain*. SQL is absurdly massive for things that could have collapse all the syntax 10x or more with more principled approach (and ACTUALLY doing relational model). However, working in an RDBM now I also understand why is not desirable to make "raw" calls to the DB: The engine MUST mediate all the calls to make things works (from query optimization, execution, iteration, lock management, transaction management, etc). Is incredible how much sophistication is in a simple `SELECT * FROM table`. What I wish is to build a `Wasm-like` IR so that is what anybody target, and `

I wouldn't ordinarily chirp about this because it seems to be such a common typo/mistake but the fact you have a badge for it <https://github.com/clockworklabs/SpacetimeDB/blob/0f1fdf62d0...> as well as typoing it down in the license section <https://github.com/clockworklabs/SpacetimeDB/blob/0f1fdf62d0...> makes it worth pointing out in hopes of correction The SPDX for BUsiness Source License is BUSL https://spdx.org/licenses/BUSL-1.1.html but the SPDX for Boost Source License is BSL https://spdx.org/licenses/BSL-1.0.html Based on a search <https://shields.io/search?q=license> it seems you're using the custom badge syntax <https://shields.io/badges/static-badge> so you have influence over the correction

We just released our database, SpacetimeDB, on GitHub under the BSL 1.1 license. It converts to a free software license after a few years. The point of the database is that you upload application logic into the database as a WebAssembly stored procedure, so instead of clients connecting to a webserver they connect directly to the database. The database itself does authentication and you write your own authorization logic just like you would inside a webserver. We’ve developed our game, BitCraft (https://bitcraftonline.com) entirely in this way. All of the game state is stored and synchronized with clients via SpacetimeDB, including player positions and movement. We also plan to allow you to horizontally scale your applications in two ways: 1. By having multiple databases that can send messages to each other (i.e. the actor model) 2. By ha

We (Clockwork Labs) have been developing this database for several years as the backend engine for our MMORPG BitCraft (https://bitcraftonline.com). 100% of the game's logic is loaded into the database and then players connect directly to the database instead of to any game server. All the data is then synchronized with the client (trees, player positions, buildings, terrain, etc). We think it will substantially decrease the complexity of deploying a live service. We've released the code under a BSL 1.1 license which converts to a free software license: https://github.com/clockworklabs/SpacetimeDB. Our Discord is: https://discord.gg/spacetimedb BitCraft is written in Unity and SpacetimeDB works out of the box with Unity, although we also support several client languages as well (Rust, Typescript, C#, Python).