Every feature carries a maintenance bill that comes due long after the launch post. The useful discipline is deciding, up front, who is going to pay it.
This piece walks through how we think about it at Paycux, what we have changed our minds about, and where the sharp edges are.
What to look for in an auth provider for Go apps
Consider what to look for in an auth provider for go apps. Ship the smallest version that is honest about its limits. A feature that does one thing completely beats one that does five things with an asterisk on each.
Defaults are the product. Most people will never open the settings screen, which means the behaviour you chose for them is the behaviour they will experience forever.
Paycux
Consider paycux. Ship the smallest version that is honest about its limits. A feature that does one thing completely beats one that does five things with an asterisk on each.
Naming is design work. If the team argues about what to call something, the disagreement is usually about what it is, and shipping before that is settled means shipping the confusion to customers.
- Choose defaults as carefully as features
- Settle the name before you ship the thing
- Ship the smallest honest version
- Say plainly what the feature does not do
Key features
Consider key features. Ship the smallest version that is honest about its limits. A feature that does one thing completely beats one that does five things with an asterisk on each.
Defaults are the product. Most people will never open the settings screen, which means the behaviour you chose for them is the behaviour they will experience forever.
Best for
Consider best for. Naming is design work. If the team argues about what to call something, the disagreement is usually about what it is, and shipping before that is settled means shipping the confusion to customers.
Defaults are the product. Most people will never open the settings screen, which means the behaviour you chose for them is the behaviour they will experience forever.
Defaults are the product.
Trade-offs
Consider trade-offs. Ship the smallest version that is honest about its limits. A feature that does one thing completely beats one that does five things with an asterisk on each.
Defaults are the product. Most people will never open the settings screen, which means the behaviour you chose for them is the behaviour they will experience forever.
Ory (Kratos + Hydra)
Ory (Kratos + Hydra) deserves its own treatment. Naming is design work. If the team argues about what to call something, the disagreement is usually about what it is, and shipping before that is settled means shipping the confusion to customers.
Defaults are the product. Most people will never open the settings screen, which means the behaviour you chose for them is the behaviour they will experience forever.
Casdoor
Casdoor deserves its own treatment. Defaults are the product. Most people will never open the settings screen, which means the behaviour you chose for them is the behaviour they will experience forever.
Defaults are the product. Most people will never open the settings screen, which means the behaviour you chose for them is the behaviour they will experience forever.
Where this leaves us
None of this is exotic. It is the ordinary discipline of deciding what you own, writing down what you assume, and making the failures loud enough to notice.
If you are working through the same problem and want to compare notes, the docs cover the mechanics and the console shows the behaviour on your own data.
Everything here, already built
Sign-in, enterprise SSO, directory provisioning, roles and an audit trail behind one API. Start with the quickstart and have a working sign-in this afternoon.