FriendlyData VS authzed

• Ease of Use
  FriendlyData allows users to interact with databases using natural language queries, which makes it accessible for non-technical users who are not familiar with complex database query languages.
• Time-Saving
  By enabling natural language processing, FriendlyData reduces the time it takes for users to get the information they need, facilitating quicker decision-making processes.
• Integration
  FriendlyData can be integrated with various platforms and services, making it versatile for different business needs.

Possible disadvantages

• Complex Queries Limitation
  While FriendlyData is useful for simple queries, it may struggle to accurately interpret and execute more complex queries, limiting its effectiveness for advanced data analysis.
• Language Ambiguity
  Natural language processing might not always accurately interpret user queries, especially if the input is ambiguous or lacks specificity.
• Dependency on Vendor
  Relying on third-party services like FriendlyData introduces dependency on the vendor for maintenance, updates, and support, which could pose risks if the service changes or is discontinued.

• Fine-Grained Access Control
  Authzed provides fine-grained access control via its Zanau authorization system, allowing for highly specific permissions and access rules tailored to complex requirements.
• Scalability
  Authzed is designed to handle large-scale applications and supports millions of users and permissions scenarios efficiently.
• Open Source
  Authzed offers an open-source approach with SpiceDB, allowing developers to contribute and adapt the platform to their specific needs while benefiting from community support.
• API-Driven
  The platform is API-driven, offering seamless integration with existing systems and technologies, making it easier for developers to incorporate into their architectures.
• Cloud-Native
  Designed for modern cloud environments, Authzed supports cloud-native development practices, such as containerization and microservices architectures.

Possible disadvantages

• Learning Curve
  Due to its detailed and customizable features, there is a steep learning curve associated with implementing Authzed, which may require more time and resources initially.
• Complexity
  The system's capability for fine-grained permissions can add complexity to integration and management, potentially complicating simpler authorization needs.
• Documentation Depth
  While improvements are continuously made, the documentation might not be as comprehensive or beginner-friendly as some users require, potentially complicating onboarding for new users.
• Dependency on External Service
  Utilizing Authzed as an external service may introduce dependencies and concerns about service stability, uptime, and third-party management.
• Early Stage
  As a relatively new entrant in the authorization space, some potential users may be hesitant to adopt Authzed due to concerns over the maturity and long-term support of the platform.

Tracking FriendlyData since Mar 2021.

• Open Policy Agent

  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... - Source: Hacker News / over 2 years ago

• Understanding Google Zanzibar and Why Shines at Building Permissions

  Plugging another company that's been implementing Google-Zanzibar-like auth tech: https://authzed.com/. - Source: Hacker News / over 3 years ago

• The developer’s guide to IAM buzzwords

  Leading Authorization services include: ⁠Permit.io, AuthZed, Ory Keto, Styra DAS. - Source: dev.to / almost 4 years ago

View more