4 ms·
I don't see anything in this article that's specific to auth. Why not entitle the blog post "Why outsource?". The points made in the article seem equally appli
by lucideer 6y ago
I don't see anything in this article that's specific to auth. Why not entitle the blog post "Why outsource?".
The points made in the article seem equally applicable to any piece of a software service. It effectively boils down to this first line of the Maintainability section:
> There are trade-offs here
- mooreds 6y agoWell, for one because it was posted on an outsourced auth provider's website :) . (Full disclosure: they are my employer.) Seriously, though, while the headlines (cost, maintainability, etc) are applicable to any non-core software functionality, the arguments below the headlines are focused on authN/authZ. Security, standards compliance, auth breach consequences: these are all factors that matter more for outsourcing auth than they might, say, outsourcing your brochure website hosting, or outsourcing analytics. All outsourcing decisions will involve some of these dimensions, but with a different emphasis.
- lucideer 6y ago> Security, standards compliance, auth breach consequences I would argue that security, standards compliance, and breach consequences apply to everything. > but with a different emphasis This is fair though.