196 karma · joined February 15, 2018
You/we are all susceptible to this sort of thing, and I call BS on anyone who says they check every little thing their agent does with the same level of scrutiny as they would if they were doing it manually.
There's a set of common needs across these gateways, and everyone is building their own proxies and reinventing the wheel, which just feels unnecessary.
~All of our customers at Oso (the launch partner in the article) have been asking us how to get a handle on this stuff...bc their CEO/board/whatever is asking them. So to us it was a no-brainer. (We're also Tailscale customers.)
ahem, he's from Utah duh bro
WARNING DANGER CAUTION GET THE F** OUT YOU WILL DIE
I have never met Steve, but this warning alone is :chefskiss:
Having spoken with the actual creators of Zanzibar, they lament the massive challenge this design presents and the heroics they undertook over 7+ years at Google to overcome them.
By contrast, we're seeing lots of the best tech companies opt for approaches that let them leave the data in their source database wherever and as much as possible [1]
[0] https://authzed.com/blog/the-dual-write-problem
[1] https://www.osohq.com/post/local-authorization
I'm founder of Oso btw.
Here's a technical post that details these implications in practice: https://www.osohq.com/post/authorization-for-the-rest-of-us
And another post that describes an alternative approach, Oso: https://www.osohq.com/post/local-authorization
(Shocker: I'm cofounder/CEO of Oso)
Agreed. You can totally keep some data in the monolith and some data in new services, and stitch them together if/as needed: https://www.osohq.com/post/distributed-authorization
Why do you think they’ve been slow?
What kinds of spreads?
- Butter + salt
- Butter + jam
- I guess butter + anything
- Brie cheese
I could go on. Try it y'all!