Show HN: PocketBase – Open Source realtime backend in one file
1–10 of 113 posts
Re: Show HN: PocketBase – Open Source realtime backend in one file
#2PocketBase is a small open source project that I've been working for the last couple of months.
You could think of PocketBase as a lightweight Firebase/Supabase alternative.
In short, it is an open source Go backend (framework and app) consisting of:
- embedded database (SQLite) with realtime subscriptions\
- backed-in files and users management
- convenient Admin dashboard UI
- simple REST-ish API
And all of this compiles to a single portable binary.
It's still a little rough around the edges, but you could give it a try and share your feedback.
Re: Show HN: PocketBase – Open Source realtime backend in one file
#3PocketBase is a small open source project that I've been working for the last couple of months. You could think of PocketBase as a lightweight Firebase/Supabase alternative. In short, it is an open source Go backend (framework and app) consisting of: - embedded database (SQLite) with realtime subscriptions\ - backed-in files and users management - convenient Admin dashboard UI - simple REST-ish API And all of this co…
This looks cool.
Re: Show HN: PocketBase – Open Source realtime backend in one file
#4PocketBase is a small open source project that I've been working for the last couple of months. You could think of PocketBase as a lightweight Firebase/Supabase alternative. In short, it is an open source Go backend (framework and app) consisting of: - embedded database (SQLite) with realtime subscriptions\ - backed-in files and users management - convenient Admin dashboard UI - simple REST-ish API And all of this co…
Nice!
It looks like you put a lot of work into this, what was the motivation behind this project? Did you not like the existing solutions available?
Re: Show HN: PocketBase – Open Source realtime backend in one file
#5PocketBase is a small open source project that I've been working for the last couple of months. You could think of PocketBase as a lightweight Firebase/Supabase alternative. In short, it is an open source Go backend (framework and app) consisting of: - embedded database (SQLite) with realtime subscriptions\ - backed-in files and users management - convenient Admin dashboard UI - simple REST-ish API And all of this co…
This is quite a cool project! Congrats on the public release.
Re: Show HN: PocketBase – Open Source realtime backend in one file
#6PocketBase is a small open source project that I've been working for the last couple of months. You could think of PocketBase as a lightweight Firebase/Supabase alternative. In short, it is an open source Go backend (framework and app) consisting of: - embedded database (SQLite) with realtime subscriptions\ - backed-in files and users management - convenient Admin dashboard UI - simple REST-ish API And all of this co…
Nice! It looks like you put a lot of work into this, what was the motivation behind this project? Did you not like the existing solutions available?
Thanks! It was initially created to be the backend for the next version of my other open source project - Presentator v3 (https://github.com/presentator/presentator).
You could read more at https://github.com/presentator/presentator/issues/183, but to summarize - I wanted something that could be self hosted with almost no additional setup and no dependency on 3rd party services.
Re: Show HN: PocketBase – Open Source realtime backend in one file
#7Looks very nice.
One thing I noticed is you are using server sent events for subscriptions. SSE have a lot of nice properties but do have one nasty limitation (from https://developer.mozilla.org/en-US/docs/Web/API/Server-sent...):
"Warning: When not used over HTTP/2, SSE suffers from a limitation to the maximum number of open connections, which can be especially painful when opening multiple tabs, as the limit is per browser and is set to a very low number (6). The issue has been marked as "Won't fix" in Chrome and Firefox. This limit is per browser + domain, which means that you can open 6 SSE connections across all of the tabs to www.example1.com and another 6 SSE connections to www.example2.com (per Stackoverflow). When using HTTP/2, the maximum number of simultaneous HTTP streams is negotiated between the server and the client (defaults to 100)."
This can lead to some weird bug reports from users.
Re: Show HN: PocketBase – Open Source realtime backend in one file
#8Sweet. How tightly is this coupled to SQLite? I’d like to embed Dolt [0] instead, specifically for the Dolthub-backed collaboration model.
Re: Show HN: PocketBase – Open Source realtime backend in one file
#9Looks very nice. One thing I noticed is you are using server sent events for subscriptions. SSE have a lot of nice properties but do have one nasty limitation (from https://developer.mozilla.org/en-US/docs/Web/API/Server-sent... ): "Warning: When not used over HTTP/2, SSE suffers from a limitation to the maximum number of open connections, which can be especially painful when opening multiple tabs, as the limit is pe…
Yes, I'm aware of this limitation, but PocketBase uses HTTP2 when combined with the --https flag (this is by go's default net/http implementation) so it shouldn't be too much of a concern.
Re: Show HN: PocketBase – Open Source realtime backend in one file
#10Looks very nice. One thing I noticed is you are using server sent events for subscriptions. SSE have a lot of nice properties but do have one nasty limitation (from https://developer.mozilla.org/en-US/docs/Web/API/Server-sent... ): "Warning: When not used over HTTP/2, SSE suffers from a limitation to the maximum number of open connections, which can be especially painful when opening multiple tabs, as the limit is pe…
Yes, I'm aware of this limitation, but PocketBase uses HTTP2 when combined with the --https flag (this is by go's default net/http implementation) so it shouldn't be too much of a concern.
First time I’ve heard about the 6 connection limit.
I’m not fully understanding the response - are you saying that the limit is not imposed if you use https? Or am I reading wrong?