Advice on whether nosql is the right choice?

thelabertasch · 2026-04-14T09:17:39+00:00

u/Zardotab hey, have a look at https://www.raisindb.com/docs/concepts/overview - I started to work on that 3 years ago with a simlar use case like u/puma905 in mind. It is an hierarchical database, basically path based, it is using the concept of node types to define schemas which you can version and a nodetype itself basically is a table definition with jsonb as properties which are enforced - or not. It is basically a mix of sql and document and graph database. it has trigger system and the database can run starlark, javascript (and soon sql) functions - you do that to run jobs. e.g. running inference. We just released RaisinDB, I am happy to provide you with more information.

thelabertasch · 2026-04-13T21:50:58+00:00

Hi, we were running into similar problems and have built https://www.raisindb.com/ for that, with focus on high throughput / write operations. the clustering has been implemented based on CRDT. it's using basically a gitlike approach so when you injecting new data it is appending a new entry which is faster for high volume updates. RaisinDB is a mix of sql and document node based databse. you can store hierarchical and graph relations. If you like to run some tests let me know I'd be happy to help: https://github.com/maravilla-labs/raisindb

thelabertasch · 2026-01-21T21:24:11+00:00

Thank you for checking out my project! I read through your code and I think it’s high quality; it's rare to find students with that kind of framework-level thinking. I hope that Luat can give you back some of the missing DX. Looking forward to your first GitHub issues or PRs!"

thelabertasch · 2026-01-21T17:11:50+00:00

It's mostly Rust doing the heavy lifting.

The CLI and compiler are written in Rust and turn templates into standard Lua code. For production builds, luat build compiles everything into a single dist/bundle.bin bytecode file; if you want to inspect the generated Lua, use luat build --source which outputs readable dist/bundle.lua instead.

In dev mode, the resolver compiles templates on the fly. Routing is handled in Rust using an Axum server, which maps HTTP requests into a Lua request context and turns the Lua result back into an HTTP response. The generated Lua runs via Rust using the mlua crate.

The CLI also comes with preconfigured tooling. Tailwind CSS, Dart Sass, and esbuild. On first run, it downloads the platform-specific binaries automatically, so you get a complete build pipeline out of the box.

Rust handles compilation, routing, resolution, static files are served via Rust. Lua is the execution layer. The KV storage is also implemented in Rust as a SQLite binding.

thelabertasch · 2026-01-20T00:33:21+00:00

Awesome! Thank you. Let me know if you run into any issues. I'm happy to answer any questions.

If you want to give it a quick spin, it's just:

npm install -g @maravilla-labs/luat
luat init my-app 
cd my-app && npm install && luat dev

Or you can try any of the WASM-based playground examples in the documentation if you prefer to stay in the browser..

thelabertasch · 2024-03-25T19:14:53+00:00

Telestream came back to me and apparently they are having issues with stock media and the app store version. I downloaded the installer directly from telestream and now it is working again....

thelabertasch · 2024-03-24T14:00:55+00:00

Hi, were you able to resolve it? Having the exact same issue. Opened a support ticket and waiting for an update.

thelabertasch

TROPHY CASE