IronFunctions VS rafiki

> Also everything was new at one time.

Hah, this is a good point, but in my eyes lots of things that were new... never really grew up and were just deprecated and died.

For example, if someone based their setup on IronFunctions, they might have run into a bit of a painful situation, seeing as the project has been largely abandoned: https://github.com/iron-io/functions

Same for a database solution like Clusterpoint, the support for which just ended and you were left to migrate away to something else: https://github.com/clusterpoint

Ergo, I'd say that it's good for others to suffer the consequences of being trend setters and making wild bets on new and risky products and to just reap the benefits of their efforts later yourself, when things are safer. If a project has survived for a reasonably long time, it's a good indicator that it'll probably keep surviving in the future as well (there was a name for this, sadly can't recall what that was).

> I’m of the opinion that lambda-as-in-serverless is an evil.

Are there any other serverless solutions that you'd recommend?

Maybe a more open cloud function solution that could also be self-hosted, should the need arise?

As far as I know, OpenFaaS might serve that niche for some, though of course there will be no cloud solutions as large as Lambda available: https://github.com/openfaas/faas

Also there used to be IronFunctions, but those seem basically abandoned at this point: https://github.com/iron-io/functions

The ledger Tron proxy is not working so you will have your money but the ledger live can't see it. I'm not sure if anyone has logged a ticket, but I do believe if you go into developer options in ledger live you can make it connect directly to iron.io and that will resolve it. Only works on desktop though. I'm also getting some other errors randomly so perhaps there are some bigger issues. Anyway, I'd suggest the dev option to check it out.

Joran from TigerBeetle here.

On the contrary, Coil's Interledger [1] project is designing for TigerBeetle, and TigerBeetle will be the core ledger database for Rafiki [2], the open implementation of Interledger.

[1] https://interledger.org

[2] https://github.com/interledger/rafiki

Thus far, most of these functionalities only existed on paper. Rafiki will be the reference implementation, bundling all of them and hence allowing not just digital wallets but any payment provider to easily enable Interledger functionalities on their accounts. And it is fully open source!

For the past three months at Coil, we have started to develop Rafiki, an open-source All-In-One Solution for Interledger Wallets. Throughout the process, we have continued to think more deeply about how we support the open-source community and the packages that we use in Rafiki and at Coil. In this blog post, we are sharing some discoveries and decisions about what we want sustaining open-source to look like at Coil.

Learn more about Rafiki and contribute to the official Rafiki source code repository.