2 ms·
For a project like this I would say pretty unlikely because the API is already free for anyone to implement and competing implementations already exist. The ma
by jpgvm 5y ago
For a project like this I would say pretty unlikely because the API is already free for anyone to implement and competing implementations already exist.
The main difficulty with a system like this is the subtlety of operating it at scale with consistent performance and global availability.
The software itself only accounts for a small portion of that.
If AWS and friends were to pick this up and offer it then they would be putting in all of that work too so there would be a lot less they get for "free" comparatively (unless they offer an inferior product). i.e it's a substantially different situation from MongoDB, etc where the software is 99% of the product.
- jakemoshenko 5y agoThis is a pretty good analysis of the situation I think. The only thing that I would like to point out is that only a description of the API is available via the Zanzibar paper. We, and other clean-room implementations, have had to fill in the gaps around what the APIs actually look like. We've even made some of our own improvements such as resource lookup by subject[0] and a filter-based delete that mirrors the read API[1]. [0] https://authzed.com/blog/acl-filtering-in-authzed/ https://authzed.com/blog/acl-filtering-in-authzed/ [1] https://buf.build/authzed/api/docs/main/authzed.api.v1#authzed.api.v1.DeleteRelationshipsRequest https://buf.build/authzed/api/docs/main/authzed.api.v1#authz...