tag:blogger.com,1999:blog-13221527.post3549980688474987673..comments2023-10-26T05:42:47.148-04:00Comments on Development tips: Role-based permissions vs. Enterprise permissionsDennis Gorelikhttp://www.blogger.com/profile/17700219093521377626noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-13221527.post-68649343285279648012011-05-20T02:38:02.946-04:002011-05-20T02:38:02.946-04:00What app did you put your role-based permissions s...What app did you put your role-based permissions system into (while working at Google)?<br />Was it Orkut?<br /><br />Did you have a name for such permissions system?<br /><br />What name did you use for what I call in this post "roles"?<br />What name did you use for what I call in this post "features"?Dennis Gorelikhttps://www.blogger.com/profile/17700219093521377626noreply@blogger.comtag:blogger.com,1999:blog-13221527.post-81700244826962605562011-05-20T02:34:36.396-04:002011-05-20T02:34:36.396-04:00There is an interesting aspect to that issue: how ...There is an interesting aspect to that issue: how people (software architects and managers) make their architectural decisions.<br />Proponents of "Enterprise Permissions" never have the patience to carefully go through all scenarios in the attempt to disprove Role-based approach and demonstrate the superiority of enterprise permissions model.<br />Typically they give up after 10 minutes discussion (we don't have time to discuss that).<br />Thoughtful discussion (or set of discussions) can eat a day or two. That translates into about one developer-week (considering that several people participate in discussions).<br /><br />On the other hand, overhead of "Enterprise Permissions" approach can easily exceed one developer-year.<br />It's just hard to notice, because that overhead is hiding behind different development tasks. Enterprise permissions complexity just taxes developers by eating ~10% of their time.Dennis Gorelikhttps://www.blogger.com/profile/17700219093521377626noreply@blogger.comtag:blogger.com,1999:blog-13221527.post-85093478133705771152011-05-20T01:57:43.009-04:002011-05-20T01:57:43.009-04:00Thanks for posting and thanks for linking.
Regard...Thanks for posting and thanks for linking.<br /><br />Regarding the solution, that's exactly how I did it in 2005-2006 at Google. The minimalistic and working solution, just the functionality that an application needs.<br /><br />Otoh, does not it reflect a certain mentality?Vlad Patryshevhttps://www.blogger.com/profile/13466586996802181998noreply@blogger.com