If you're a solo developer or part of a small team, let me introduce you to one of the best-kept secrets in backend development: PocketBase. - Source: dev.to / 9 days ago

I have a bit of an obsession with finding the fastest way to launch apps. My goal is to be able to create fully functional MVP's and proofs of concept in less than a day. That means being able to spin up a backend and then implement a frontend as efficiently as possible. For the backend, PocketBase has been my favorite lately. On the frontend I am still trying to find a winner. I like Quasar (VueJS + Capacitor)... - Source: dev.to / 14 days ago

Are you aware of pocketbase? https://pocketbase.io/ I think it could work for your usecase, even though its generally focused on being a backend. I have had a very nice experience. - Source: Hacker News / 2 months ago

For quick prototyping I really like https://pocketbase.io/ I am actually using this for a production site that gets 1 million requests per day. - Source: Hacker News / 3 months ago

Pocketbase is a lightweight, open-source backend solution that combines a real-time database with file storage and authentication services. Its key benefits include simplicity and portability, as it can be run locally or in the cloud without much overhead. Designed to be user-friendly for both small projects and rapid prototyping, Pocketbase makes it easy for developers to quickly deploy applications with built-in... - Source: dev.to / 7 months ago

The problem with HTTP2 is that the server-push aspect was tacked on top of an existing protocol as an afterthought. Also, because HTTP is a resource transfer protocol, it adds a whole bunch of overheads like request and response headings which aren't always necessary but add to processing time. The primary purpose of HTTP2 was to allow servers to preemptively push files/resources to clients to avoid round-trip... - Source: Hacker News / about 1 month ago

For WebSockets, using SocketCluster (https://socketcluster.io), it's possible to queue up all requests from the same client and then detect and respond to high backpressure spikes (e.g. By disconnecting the client and/or recording the incident). You can combine different approaches like limiting the number of connections from a single IP within a certain timeframe and also limiting the backpressure. The ability to... - Source: Hacker News / 9 months ago

I never fully understood the need for back end message queues TBH. You can just poll the database or data store every few seconds and process tasks in batches... IMO, the 'real time' aspect was only ever useful for front end use cases for performance reasons since short polling every second with HTTP (with all its headers/overheads) is prohibitively expensive. Also, HTTP long polling introduces some architectural... - Source: Hacker News / 11 months ago

Recently, I added an AI-generated soundtrack to my open source project's home page https://socketcluster.io/ It seems unconventional at first but I distinctly remember about a decade ago when Adobe Flash was still broadly supported, many Flash websites had soundtracks. I think the reason why regular HTML websites didn't have them was because it was difficult to implement and internet was much slower so they had to... - Source: Hacker News / about 1 year ago

I wrote an async/await stream library for JavaScript/Node.js which supports backpressure management. It's heavily tested and used as part of SocketCluster (pub/sub SDK) https://socketcluster.io/. - Source: Hacker News / about 1 year ago