Developers who stop by our conference booths frequently say “We wish we had known about Stormpath a year ago before we started our project.” Fortunately, it’s actually easy to switch out a homegrown identity service to an Identity API.
When they first scope out a new web or mobile application, engineering teams often choose to build Identity Management in-house for the initial release. This happens for a variety of good reasons:
There are many reasons “proof-of-concept” or homegrown authentication services make it into the actual product on launch day. When does it make sense to revisit?
Post-launch, authentication – and particularly authorization – features can cause maintenance headaches. Business requirements expand, and functionality gets bolted on. But maintenance headaches also strongly affect the operations teams. Ops has to ensure the necessary availability and scalability to provide a positive experience for end users. Spiky, event-driven usage patterns can really wreak havoc on Identity infrastructure, and not every ops team wants to take that on.
Fortunately, the decision to roll your own user management is not irrevocable; you can still swap in an API service like Stormpath. In fact, the majority of our customers did just that, and here’s why:
Cost savings: User management is one of the highest-risk areas for cost overruns, both for the maintenance phase and initial development.
To switch or not to switch? If you struggle with this choice, our new white paper may help; Of course, an outside Identity Management API is not for every team or every project. There are valid reasons why you might not want to swap out your homegrown approach. The white paper examines those reasons as well.
Download our new white paper, “User Management for Web and Mobile Applications: Why Teams Replace Homegrown Identity” here (registration required).
If you would rather have someone email the white paper to you directly, just drop us a note at [email protected].