postgrest-rs VS coolify

Supabase: Build modern apps with a scalable backend.

In the db.ts file we are going to create our database connection, in my case I will occupy (Supabase)[https://supabase.io/], but you can occupy any database you want.

Head over to Supabase and create a new project. Once the project is set up, navigate to the SQL section and create a new table for your todos:

I integrate supabase to my side project. Use the crate postgrest-rs.

Supabase

Since I went out of the dynamic properties, now it doesn’t automatically store my file in a cloud storage provider (Supabase) anymore. So I need to do it manually:

Authentication & Database: Supabase

- they use more cost efficient hardware (e.g. databases running on 3rd gen SSD disks) to run your workloads.

Since these companies are renting raw hardware, on which they run your workloads (and are not using cloud-provider-native services, such as RDS), they need to hire experienced operators able to run and manage those workloads in production. This (for obvious reasons) is not exactly easy, and requires a lot of experienced talent with operational experience.

Hiring those people is very hard, as these experts are not usually available on the market.

This leaves us with with the obvious problem:

Are the operators of the given PaaS provider really able to run your production workloads? Are they able to to withstand all the issues that may arise?

Don't get me wrong. There definitely are companies (the most succesful) able to hire very capable talent (such as https://supabase.io), but this definitely isn't the case for all of those PaaS providers.

And I believe that these companies will need to increase their prices (and be less lucrative for their customers) or changes their business model.

This is something that we at stacktape.com built our business case on. We took a different path. We just wanted to make the existing (AWS) offerings 2 orders of magnitue easier to use, so that any developer (withou Cloud or DevOps experience) can use them productively.

We're not running your workloads for you. We are just making AWS services (run by experienced operators) significantly easier to consume (97% less difficult, so that any developer can do the job). For that, we're charging 30%->20% of the AWS infrastructure costs managed by us premium. This also means that you are not restricted to our platform, but can easily extend your infrastructure by any AWS service (using AWS CloufFormation or AWS CDK).

AWS offers areasonably generous free tier, and Stacktape won't charge you for any resources withing the free tier.

We're launching our v2 soon (~1-2 weeks), and if the offering we have sounds interesting, we'll be very happy to hear your thoughts.

You can there is a client library for Postgres for rust. There aren't all the other clients, but perhaps you can help the community build them.

This is my first quick try deploying SvelteKit with the open source software Coolify by Andras Bacsai.

With a serverful approach, you can avoid these drawbacks, and the main challenge lies in selecting the platform that aligns with your requirements. Options may include AWS, Render, DigitalOcean, and others. While VPS is also an option, it's generally not recommended due to the significant setup and maintenance overhead involved (logging, monitoring, CI/CD pipelines, etc.). However, you can make your life easier by leveraging tools like Coolify that help managing your VPS.

Heroku and similar providers can simplify the server management issues, but you can use something much better that can combine both cost efficiency and ease of deployment—Coolify:

> VPSs being “easy to manage” is a strong option full of assumptions.

There are definitely many footguns with managing a VPS but I think the threshold to get vaguely competent with a VPS is not really that far off with getting familiar with the average cloud platform - which comes with its own dangers, like the near-total inability to put an upward cap on fees that that person found out with Netlify recently.

Having a $5 VPS and knowing it's never going to cost your more than $5 might balance out a lot of things on the other side for a lot of people.

(And, as a bonus, it comes with the benefit of having a better idea of what is going on on the actual computer which is running your code.)

Platforms like https://coolify.io/ (which I have not tried, but looks interesting) seem to give you some of the abstractions that you get in cloud platforms to save you having to mess with too much low level stuff and become an expert in a billion separate systems.

If you have Debian with automatic updates that does most of the heavy lifting for you. The hardest problem I have is resisting the temptation to just install everything, because the cost to do it is capped at my VPS monthly fee.

So yep, it comes with a lot of assumptions. But so does everything!

https://coolify.io/ might be worth a look

The modern iteration of these tools has taken the developer experience learnings from the Platform as a Service (PaaS) category, and will bring them to your own VM, giving you your own personal PaaS. Example of this include Dokku, Coolify, Caprover, Cloud66 and many more!