Transport for London does the same. If you add your (real, CPAN) card number to the "Contactless and Oyster" web service, it will also add all of the DPANs you have tapped in with on their network as separate cards.
I recently discovered PocketSmith[0] which is not free nor open-source, but I have found it to be the easiest to keep up to date. It automatically pulls transactions from most banks and credit providers, which I've been unable to replicate with other solutions.
A nice write-up, however it looks to me that the Compute@Edge tests were being run on a free tier service (adding a credit card to Fastly account does not upgrade your service automatically, I know because I work at Fastly).
I'd love to see results from the same tests run on the full version of the platform.
Forgive me if I'm misunderstanding, but this looks like an end-user authentication system that you would implement in your own app rather than a corporate directory like Okta. Different use cases.
Sorry, I was trying to clarify in my comment but failed to put it through clearly. When I say "We ran our own benchmark" I mean Fastly ran a benchmark on a Fastly Compute@Edge service.
To clarify, Fastly did not perform any benchmarks on Cloudflare's network. We ran our own benchmark, comparable to the one that Cloudflare ran on our platform, and compared those results to the ones that Cloudflare published as part of the original blog post.
The Cloudflare terms prohibit benchmarking without their explicit permission.
It definitely comes down to the language — JavaScript is an interpreted language, which requires an engine. Rust is statically compiled and runs by itself.
An unfortunate comparison at the start there, considering that the "native" and recommended language for performance on Fastly Compute@Edge is Rust. JavaScript support is in beta.
Try the experiment again with a Rust service compiled to WebAssembly and I'm sure the results will speak for themselves.
I am a big fan of Fig. Some of my favourite specs are `docker` and `git`. No longer do I need to list containers or commits before performing an action, the autocomplete provides all of these values for me.
I'm excited to see more command-line tools provide metadata about commands close to the source code. Our CLI at Fastly provides JSON output in the help command, so it was really easy to generate a Fig spec automatically: https://github.com/kailan/figly