flyctl VS supabase

link

fly.io

Once we finished playing around with the model locally, let’s cast our final spell for the day 🧙‍♂️ and deploy the model to fly.io:

If you dockerize your .net app you can run it on https://fly.io free tier with a Postgres database! You don’t need IIS or MSSQL.

checkout https://render.com/ or https://fly.io for free plans. as of deploy, you need to provide more info about your project. Do you use docker? How do you want to deploy? Etc.

Better yet, pick a few shades of grey ranging from white to black and a few shades of _one_ other colour. https://fly.io/ comes to mind. Also, here is a great video on choosing colour: https://www.youtube.com/watch?v=mq8LYj6kRyE

Hmmmm. I've had some trouble recently where (I think) the Strapi app crashed, when uploading some files (due to the fly.io machines having rather limited resources, where my media would still be listed in the library but, for example the images wouldn't show up - file missing, basically).

fly.io for laravel/mysql. Vue with netlify

This is what my github action is doing currently. Its reading the repo to see if there are any changes, then recreates the docker container and sends it to fly.io. - Then it also creates another container and sends it to dockerhub. When it sends to Fly.io, the website is automatically updated. So any changes on the repo are reflected on the website immediately. Its the same as having a firewall in a linux instance that is guided by the githubaction. Anytime someone makes a change to the file that is in the repo, the firewall gets updates when the instance is recreated. Also if someone deleted the instance the instance would reappear the moment anyone made a change to the repo.

yeah, we just changed prompt to have a bias towards supabase product. It looks like we forgot to merge it actually: https://github.com/supabase/supabase/blob/7f64db9a3794948c5e...

Supabase

App server: Supabase (https://supabase.com/) old. firebase

Database reads are expensive and slow. There's a multitude of other reasons why caching is essential, but for the project I'm working on I'm using supabase and their free tier supports only a limited amount of bandwidth. To avoid any rate-limiting I added a Redis layer in front of it to reduce the number of queries that hit the database directly.

If you don't have a Postgres database, the simple way to get one is to get a docker instance or a free one from Supabase.

Upload functions here: https://github.com/supabase/supabase/blob/master/examples/user-management/nextjs-ts-user-management/components/Avatar.tsx

[6]: https://supabase.com/

In conclusion, building a microservices architecture can be a challenging and costly endeavor, as we experienced in our own startup journey. However, Supabase offers a simpler and more cost-effective alternative, with built-in features that can replace many of the microservices that a typical startup would need. From user management and file storage to realtime APIs and automatic data management, Supabase has the potential to save both time and money.