pebble VS Ory Hydra

At Canonical I work on two open-source projects written in Go: Juju, a large cloud-based application deployment tool, and Pebble, a small Linux service manager. Both include CLI clients and API-based server daemons. Juju in particular is a large distributed system.

Yeah, I like the "visual boundaries" way of framing it. A line of whitespace is a visual boundary, of course, but I find the // comment above it acts as a heading. Like a bold heading above a couple of paragraphs of text in a document.

I wouldn't add a heading above every paragraph, but I would might above every few paragraphs. In code, this translates to every 5-15 lines of code. Here's some code I wrote recently that shows this (https://github.com/canonical/pebble/blob/b152ff448bbe7d08c39...):

    func writeFile(item writeFilesItem, source io.Reader) error {

OAuth Server - Hydra

For examples of my work see my contributions to Ory Hydra https://github.com/ory/hydra.

I'd be more than happy to talk about how I can bring value to your project. Let's have a conversation!

Another package you might want to consider is ORY Hydra. https://github.com/ory/hydra

Check this project: https://github.com/ory/hydra

> 10k M2M tokens for $250/month sounds like a really bad deal if I can just spin up https://github.com/ory/hydra that can easily handle 10k requests per second.

Spinning one up is easy, sure. Making sure it's production ready, is not so much.

Have not tried Dex so can't speak to that.

https://github.com/ory/hydra