buildpacks VS dbmate

You're better off using Cloud Run. In some ways, it's easier than App Engine. You can use a buildpack (blog, blog, GitHub) to automatically build a docker image with Go using the code you provide. You can then configure Cloud Run to allow up to 60 minutes of time per invocation.

Under the covers this uses Google Buildpacks to create a container image from your app: https://github.com/GoogleCloudPlatform/buildpacks

Cloud Build is indirectly called to containerize your app. One of its core components is Google Cloud Buildpacks, which automatically builds a production-ready container image from your source code. Here are the main steps:

This explicitly uses the Buildpacks provided by Google. You can find more information about these on Github

The function is containerized using Google Cloud buildpacks.

As for being able to run your own instance of things in isolation, that really depends on the fidelity you want. Firebase has an emulator you could use, and Cloud Functions/AppEngine can be built into docker images locally using the public buildpacks (but won't have the full suite of attached services), but I'd probably recommend good service mocks/stubs/fakes your services plus a pipeline that spins up a full project with Terraform, runs integration tests, then tears it down for e2e testing.

A regular code repo with the scripts (with pull/merge requests for review) and then a CI job that builds containers with something like dbmate https://github.com/amacneil/dbmate that can then be run against any staging/prod environment.

As we want to maintain the track of our changes to the DB, we are going to use migrations. In this case, we are going to use dbmate. But, you can use any other tool you want.

> For example having database migrations built in etc.

I actually went the exact opposite route, at least when possible: https://github.com/amacneil/dbmate

Pure SQL migrations, regardless of the back end technology that you use, completely decoupled from how each framework/library views things and therefore not dependent on them (you could even rewrite the back end in another technology later on, if needed; or swap ORMs; or avoid issues when there's a major ORM version update).

It's really nice when you can generate entity mappings based on a live database, like with https://blog.jetbrains.com/dotnet/2022/01/31/entity-framewor...

So in my case, I can have:

  * a DB that has migrations applied with dbmate, completely decoupled from any back end(s) that might use it

You can run dbmate as part of your CI/CD pipeline. You just keep a dbmate directory in your repo and deploy migrations with your code.

In general with ORMs, you will face a problem in one way or another. I ended up simply using https://github.com/gajus/slonik and https://github.com/amacneil/dbmate for migrations. My life is way much better since then.

I like dbmate, super simple and straightforward to use. For your specific use case, it can also be configured using your .env!

Would always go for a language agnostic migration tool, e.g. https://github.com/amacneil/dbmate to stay flexible and stay away from lock-in effects (besides sql).