docs VS postgrest-rs

🔗 Courier Docs

In this article, I will be integrating Courier to send emails for this project.

Courier Documentation

With that said, we believe that in order to make software-to-human communication delightful, there needs to be an open line of communication with developers who have implemented Courier to handle their notification infrastructure. We want you to have as many support options as possible whether it’s self-serve through our docs and articles, or 1-1 with our engineers and support staff. We’re here to make your Courier experience as smooth as possible! If you’d prefer enterprise-level support, sign up for a demo request now!

There are a few more goals we have for our documentation. We have yet to utilize Docusaurus’s localization feature, so that’s in the works. We have also recently made our documentation open-source to welcome external contributors. This way, the user can take ownership of the updates they want and help themselves and others who would benefit from their contribution.

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.