Summary of Articles Referenced When Considering Auth0 Adoption

I’ll introduce articles I referenced when starting to use Auth0.

Background: Want to Start Using Auth0

There was a development project where I wanted to use Auth0 as an IDaaS, and this article summarizes the content I researched.

Auth0 Implementation Track Record

The implementation cases at the Ministry of Economy, Trade and Industry and NTT Docomo seemed useful for explaining to provide confidence when adopting Auth0.

SaaS-type authentication solution Auth0 introduced for G-BIZ ID integration in Ministry of Economy, Trade and Industry project｜Auth0 Inc. Press Release
Docomo's "IDaaS" implementation story　The battle with bosses who say "authentication mechanisms are simple" and "we can develop in-house, right?" (1/2) - ITmedia NEWS

Auth0 Supported Regions: America, Europe, Australia

Conclusion

Speed priority: au Australia
High availability: us America

Reference Information

Finding the optimal Auth0 region for Asia (Tokyo) | Developers.IO

Currently, Auth0's public regions can be selected from three: America, Europe, and Australia. When accessing Auth0 from a data center in Tokyo, I want to consider which region to choose based on login time. By the way, Auth0's community recommended Australia, which is geographically closer.

Summary
Based on accessing each region’s endpoint every minute and looking at the average execution time over 24 hours, the Australia region was the fastest. While I accessed two endpoints this time, if we consider execution time as the criterion, selecting the Australia region from Tokyo seems to be better. However, looking at the average and percentile graphs, the America region has the least fluctuation. This might mean it’s stable regardless of time. As mentioned in the reference section, the America region adopts multi-region high availability architecture. I couldn’t find information about other regions. I’ll add updates once I can confirm.

About Auth0 Backup

https://dev.classmethod.jp/articles/strategic_auth0/#toc-13

Q. "Is it necessary to backup Auth0 user data elsewhere? If so, I'd like to hear about best practices." A. Auth0 also backs up user data to different data centers, so normally customers don't need to take backups, but it's also possible to obtain user data via export API. https://auth0.com/docs/api/management/v2/#!/Jobs/post_users_exports

Auth0 Status Page

https://status.auth0.com/

SLA

At minimum, SLA 99.90% appears to be guaranteed.

The average availability of the Auth0 platform in each month will be at least 99.90%. https://auth0.com/docs/support/services-level-descriptions

Auth0 Reference Articles

Below are articles I referenced for trying Auth0, customization, and writing sample code. This is mostly a collection of links from Classmethod’s technical blog.