Policy Language Showdown: AWS Cedar vs. OpenFGA

Slack Community ► bit.ly/permit-...
​Discover the world of policy languages with the co-creators of AWS Cedar and OpenFGA! Learn about their creation, application, pros, cons, and how to choose the right one for your needs!
We will discuss:
​- The unique experience of creating a new “programming” language
​- The importance of decoupling policy from code
​- What developers gain from "Everything as Code"
​- The Pros and cons of creating a new language
​- Solving the learning curve barrier for developers who don't want to learn a new language
​- Policy as Graph vs Policy as Code
​- How do you choose the right language for your needs?
​- Does using both languages make sense?
​- Live Q&A
​Join us for an exciting discussion about the world of policy languages with the co-creators and product managers of AWS Cedar and OpenFGA. Our speakers will share their unique experiences creating these new "programming" languages and discuss their importance in decoupling policy from code.
For further reading:
www.permit.io/...

[@NaveenSiddareddy]

- consistency in FGA is mainly around how long does application take to write relation into graph. On the flip side, i still dont get sending data every call to Cedar engine as much as i like that policys are vetted using math
Ultimately, it plain data modeling exercise(entity, relation) that has been used from ages when building applications , its just that we want to add authorization (rules) to the mix !! modeling cant be offsourced to vendors, its business domain , please make this modeling exercise easy atleast use SQL or Cypher and accommodate conways law into it