Re:Open Policy Agent
by AgentOrange1234 on Tuesday March 12, 2024 @07:03PM
(#39685983)
Seems pretty damning. Why would someone choose Cedar? Is there some upside that isn’t captured here?
[ Parent
| on HN ]
AWS uses it and the policy language is similar, and if you are all in on AWS, then it makes sense to keep it for consistency?
There is actually pretty vibrant and diverse Cedar community. Check out their slack.
Re:Open Policy Agent
by i_play_stax on Wednesday March 13, 2024 @05:07AM
(#39689390)
https://docs.opal.ac/
Universally, people I've met and worked with (20-30) hate writing rego (OPA).
I'm always skeptical of Styra's analysis; they are literally selling you something.
AuthZed looks interesting and they have good "ride along" videos in YouTube, e.g. replicating GitHub auth.
The benefit of Cedar mainly comes down to the language. Cedar was designed to sit in the middle of a runtime call, so it has reliably low latency (see comparison here: https://twitter.com/Sarah_Cecc/status/1766141060370329748) even at high scale. It's way more readable so it's easier to author and debug. And it's validated against formal methods proofs so certain properties of the language (like default deny) are mathematically proven.
More about the benefits of Cedar here: https://cedarland.blog/design/why-cedar/content.html