crane VS shipit-engine

For example: shipit was a homebrew deployment system Shopify made, and they open-sourced it because there's nothing about how they ship their code that's a trade secret or worth hiding.

> Usually that was in the form of long-running network calls.

That's why doing a network call to another service in the middle of a request is pretty much banned from the monolith. Anything that doesn't have a strict SLO is done from background jobs that can take longer, be retried etc.

Now you mention FedEx so I presume you were working on the shipping service, which by essence is kind of an API bridge so it's probably why it was deemed acceptable there, but that's far cry from what a typical Rails app look like, except maybe in companies that do a lot of micro-services and are forced to do inline requests.

> that's not a use case that Ruby/Rails are built to elegantly handle.

I'd argue the contrary, the elegant way to handle this is to perform these calls from background jobs. Look at shipit [0] for instance, it's syncing with the GitHub API constantly but doesn't do a single API call from inside a request cycle, every single API call is handled asynchronously from background jobs.

[0] https://github.com/Shopify/shipit-engine/

My team is evaluating different deployment tools to replace our homegrown solution.

There are plenty of continuous integration tools (GitHub Actions, CircleCi, etc.), but adding deployment aware logic like canary deployments and having an audit log of deploys requires adding lots of code which I'd rather not maintain.

I'm looking for tools focused on code deployment. A quick search turned up shipit (https://github.com/Shopify/shipit-engine) and teletraan (https://github.com/pinterest/teletraan).

Are there other open-source deployment tools like those projects?