roadmap VS flyctl

In case anyone is interested, Heroku finally released pgvector support for Postgres yesterday: https://github.com/heroku/roadmap/issues/156

Pgvector is an extremely excellent way to experiment with embeddings in a lightweight way, without adding a bunch of extra infrastructure dependencies.

(I work at Heroku) Do you have more details on what sucks? Anything we're not already tracking to fix in our public roadmap? https://github.com/heroku/roadmap/issues

"GitHub - heroku/roadmap: This is the public roadmap for Salesforce Heroku services." https://github.com/heroku/roadmap

You can upvote here to try get a version of free back - https://github.com/heroku/roadmap/issues/51

I proposed this -> https://github.com/heroku/roadmap/issues/51 on the Heroku roadmap - hopefully to bring back some sort of free trial environment. Please take a look an upvote if you agree:

The public roadmap is a good idea but highlights how stale the product has become. https://github.com/heroku/roadmap/issues Only now researching adding Cloud Native Build Packs and HTTP2.

This will reaffirm for many the sense that Heroku is being dismantled from within. Feature sunsetting and removal of a free on-ramp doesn't help.

If you're looking for a production alternative to Heroku checkout Northflank.

https://northflank.com

To begin visit fly.io to create an account. Next install flyctl a command line tool for creating and deploying fly apps. macOS

For frontend deployment, I used Netlify (for the generous free package) and the recommended fly.io for server + database (also cheap package).

Create an account on Fly.io.

You can learn more about fly.io and tigris, we will need to create an account on both platforms for this project regardless. Anyway with the theory out of the way let's get started in the next section as we create our accounts and start building the app.

Fly.io is a platform that helps you run your apps and databases closer to your users all around the world. It takes your app code, packages it up neatly, and puts it on virtual machines that can be quickly started or stopped. This makes your app faster for users and more reliable. Fly.io is easy to use, works well for small projects or personal apps. It's a great way to make sure your app runs smoothly for people no matter where they are.

In this post, we'll start from scratch, running FerretDB locally via Docker, trying out the connection with mongosh and the MongoDB Node.js client, and finally deploy FerretDB to Fly.io for a production ready set up.

2- fly.io

Fly is a cloud platform that focuses on global edge computing. Fly specializes in high-performance hosting and provides a global network of edge locations. Fly is known for its scalability and performance optimizations.

But videototextai.com is built using NextJS + Firebase auth + Firestore and a backend deployed at fly.io . Fly makes it really easy to deploy docker containers and that is IMO the fastest way to develop, you can setup a local setup

Alternatives explored: * northflank: While running the wrk test, requests were taking 3-7 seconds. Couldn't repeat Heroku's phenomenon of "400ms-800ms" during such a load test. * fly.io: Reliability: It’s Not Great * render.com: I remember the time when indiehackers.com was down because of an outage on Render, not sure if it's worth trusting.