The first reason is that serverless architectures are inherently scalable and elastic. They automatically scale up or down based on the incoming workload without requiring manual intervention through serverless compute services like AWS Lambda, Azure Functions, or Google Cloud Functions. - Source: dev.to / 15 days ago

The FaaS platform gained a lot of popularity which resulted in many competitors. There was OSS providers like OpenFaaS or Fission. There were of course the commercial versions to like Azure Functions and Google Cloud Functions. - Source: dev.to / 23 days ago

One of the issues developers can encounter when developing in Cloud Functions is the time taken to deploy changes. You can help reduce this time by dynamically loading some of your Python classes. This allows you to make iterative changes to just the area of your application that you’re working on. - Source: dev.to / 6 months ago

I've been looking at Google Secret Manager which sounds promising but I've not been able to find any examples or tutorials that help with the actual practical details of best practice or getting this working. I'm currently reading about Cloud Functions which also sound promising but again, I'm just going deeper and deeper into GCP without feeling like I'm gaining any useful insights. Source: 8 months ago

Serverless computing was also introduced, where the developers focus on their code instead of server configuration.Google offers serverless technologies that include Cloud Functions and Cloud Run.Cloud Functions manages event-driven code and offers a pay-as-you-go service, while Cloud Run allows clients to deploy their containerized microservice applications in a managed environment. - Source: dev.to / 10 months ago

The logo is already taken by https://pocketbase.io. - Source: Hacker News / 8 days ago

Pocketbase - Never used before but it says in their home page the following: "Open Source backend for your next SaaS and Mobile app in 1 file". Seems porwerful. - Source: dev.to / 11 days ago

Solutions like pocketbase and coolify come close to solving these problems. However, I wouldn't choose either as I fear architecture lock-in as much as vendor lock-in. Especially in the case of pocketbase, I may be forced to rewrite my application if it were to scale overnight. - Source: dev.to / 25 days ago

Now, I've released the Gowebly CLI v2.5.0 which includes PocketBase framework/backend support. - Source: dev.to / 26 days ago

Pocketbase [0] is a possibility. It offers a way to subscribe to collections, meaning the client will be notified if any of the records in that collection change. [1] Should be quite efficient too, the FAQ claims that 10k realtime connections on a small hetzner VPS is no problem [2] [0] https://pocketbase.io/. - Source: Hacker News / about 2 months ago