News for hackers. Stuff that matters.
Re:Patterns for authorization in microservices by wizwit999 on Friday December 17, 2021 @07:12PM (#29599961)
Nice. Think of all the work that AWS puts into IAM, all the other services use it for auth.
Re:Patterns for authorization in microservices by titive on Friday December 17, 2021 @12:35PM (#29595418)
Are you aware of other (non-Zanzibar) implementations of Pattern 3?
Re:Patterns for authorization in microservices by gkaemmer on Friday December 17, 2021 @01:01PM (#29595779)
Yeah, although mostly variations on that basic premise.

Airbnb Himeji: https://medium.com/airbnb-engineering/himeji-a-scalable-cent... Carta's AuthZ system: https://medium.com/building-carta/authz-cartas-highly-scalab... Slack's architecture is a bit different, but solves some of the same challenges: https://slack.engineering/role-management-at-slack/

I've also talked to a number of teams who just implemented pattern 3 internally with a custom service. Generally they've determined it's worth it to centralize all authorization data (like roles, groups, etc) into one place and perform ALL permission checks there.

There are also some companies building essentially Zanzibar clones, like Auth0, Authzed, Ory Keto, and a few more.

Re:Patterns for authorization in microservices by jamesunderhill on Friday December 17, 2021 @02:24PM (#29597142)
seems to be a pattern of problems for most microservices