← Back to context

Comment by remram

2 years ago

I am a bit confused, is it the backend's backend? E.g. something that is used by the HTTP server app, like a DBMS would be?

Or is it actually the backend, e.g. the frontend (browser) talks to it directly?

5 comments

remram

Reply
kisamoto  2 years ago

It can be the backend itself if you just need auth (both authentication and authorization) and your SQL tables to be a REST API. This often suits frontend single page applications in JS/TS and Pocketbase also provides a JS SDK to ease this (with realtime updates). It's a similar model to Firebase but without the lock-in.

However if you want to write more logic you can also import Pocketbase as a library and extend it with hooks, custom endpoints etc. all written in Go.

Edit: Added more info about using Pocketbase with a JS SPA frontend.

  • szundi  2 years ago

    Every tech/stack is a lock-in, you just pay with different currencies and get different challanges at different stages

ilrwbwrkhv  2 years ago

You would use it instead of things like Supabase and Appwrite. It gives you a server, a db and easy authentication, authorization with real-time queries like firebase.

  • remram  2 years ago

    Maybe it's not for me, I really don't know what that means. If it only describes itself as "a replacement for <name>" I feel like I'm not the target at all.