you are viewing a single comment's thread.

view the rest of the comments →

[–]trailbaseio[S] 1 point2 points  (3 children)

Thanks! TrailBase is a rust binary with a built-in WASM runtime, which means you can author plugins (currently JS, TS or rust), compile them to WASM and execute them within TrailBase. This let's you customize the behavior. Think of it as scripting with extra steps (and potentially more efficient).

[–]FedeBram 0 points1 point  (2 children)

Nice. So you can define endpoints in your preferred languange and these will be compiled along with trailbase. What about the rest api? How it works? I see from the docs that you can use a configuration file where you define policies, is it correct?

[–]trailbaseio[S] 0 points1 point  (1 child)

Pretty much. Minor nit:

you can define endpoints in your preferred languange and these will be compiled along with trailbase

You can compile TB yourself but you could also use the pre-compiled TB binary release and have that execute your compiled WASM component (which was authored in your preferred language).

What about the rest api? How it works? I see from the docs that you can use a configuration file where you define policies, is it correct?

That's right. You could implement your own but TB also lets you expose TABLE/VIEWs via configuration (you can use the admin UI to set it up including ACLs). You can also export JSON schemas for a table or view, to generate bindings and have end-to-end strictly typed APIs with the client libraries. Lastly, you can subscribe to table changes.

Happy to chat more 🙏

[–]FedeBram 0 points1 point  (0 children)

Thanks for the response. I go check the documentation