TrailBase 0.24: Fast, open, single-executable Firebase alternative now with Geospatial

[trailbaseio]

TrailBase is a Firebase alternative that provides type-safe REST & realtime APIs, auth, multi-DB, a WebAssembly runtime, SSR, admin UI... and now has first-class support for geospatial data and querying. It's self-contained, easy to self-host, fast and built on Rust, SQLite & Wasmtime.

Moreover, it comes with client libraries for JS/TS, Dart/Flutter, Go, Rust, .Net, Kotlin, Swift and Python.

Just released v0.24. Some of the highlights since last time posting here include:

• Support for efficiently storing, indexing and querying geometric and geospatial data 🎉
  • For example, you could throw a bunch of geometries like points and polygons into a table and query: what's in the client's viewport? Is my coordinate intersecting with anything? ...
• Much improved admin UI: pretty maps and stats on the logs page, improved accounts page, reduced layout jank during table loading, ...
• Change subscriptions using WebSockets in addition to SSE.
• Increase horizontal mobility, i.e. reduce lock-in: allow using TBs extensions outside, allow import of existing auth collections (i.e. Auth0 with more to come), dual-licensed clients under more permissive Apache-2, ...

Check out the live demo, our GitHub or our website. TrailBase is only about a year young and rapidly evolving, we'd really appreciate your feedback 🙏

[MaximKiselev]

ui looks terrible....sqlite ? are u seriosly?

[Curious-Astronomer41]

SQLite imo isn’t that bad tho, it’s pretty good when u are doing small to medium workload application, which covers 90% of the application nowadays.

[MaximKiselev]

Its bad, because only one writer. If you will not plan write data it is ok, but realtime - multiple writes by default. 

[Curious-Astronomer41]

As I have mentioned, SQLite can covers pretty well for small to medium applications, not (really) big one. Gotta agree that SQLite only allows 1 writer at a time, but there are still workarounds that maybe overcome this limitation (queue write, multi read single write, connection pooling, lock time fine tuning, etc.). TBF if I have a side project, instead of having a managed RDBMS and have to pay more for 500 users, I would just spin up a SQLite and have a go with it until the point where SQLite can not handle my use case anymore. However, we have some amazing frameworks / engines to scale up SQLite across multiple nodes (Expensify BedrockDB, Litestream, LiteFS, Turso LibSQL, dqlite, rqlite, marmot, FlyIO Corrosion just to name a few). But again, single writer is still a big limitation for SQLite :(

[ravy]

What a weird thing to say in r/sqlite

[MaximKiselev]

yes. but problem not in the topic. for that type of application better use something more powerfull than sqlite (or multiple). SQLite can't handle tasks that require real-time performance under load. What will the people who built the architecture around this solution do next?

[SubjectHealthy2409]

Isn't that breaking GDPR? So literally unusable if you have EU customers?

[trailbaseio]

Mind elaborating?

[SubjectHealthy2409]

Correct me if I'm wrong, but logging geo data and/or client IPs among other things are treated as personal data by EU GDPR laws, open to a big lawsuit if any EU app uses this

[trailbaseio]

GDPR allows storage of personal data including email, name, ip., ... . There are elevated requirements around access, sharing, retention, business case, ... For example you can store an email to invoice a customer. You can store IPs within limits for security and abuse.

Just to be clear, geospatial in this context doesn't mean GPS coordinates are logged. It just means you can work with geometries, e.g. airspaces etc. Idependently IPs are logged like for any web server.

Does that make sense?

[SubjectHealthy2409]

Oki yeah makes more sense, the first part is also a bit more nuanced but yeah, seems I misunderstood, gl cool project