In this special sponsored edition of ProgrammableWeb's Developers Rock podcast, Curity.io CEO and co-founder Travis Spencer explains to ProgramambleWeb editor-in-chief why he thinks its a better idea to rely on a dedicated appliance (or cluster of them) to handle identity management (OAuth, OpenID, etc) for API access. Stealing a page from the telecom industry where the infrastructure must not only scale, but cannot fail, Curity.io's approach to API identity management is modeled after the design of routers that do only a few things, but do them really really well. This is a bit different than relying on a feature within an API management system where the complexity can impact both the availability and the ability to easily scale as the demand grows. When you take an appliance approach, you essentially just add more appliances. The best part is that Curity.io is plug and play with most existing API management gateways and API management systems. For a full text transcript of this interview, go to:
0 Yorumlar