Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • 1
    3 is bad, 4 is worse (seriously, Auth0 is wonderful). Keeping everything on the server side is a much better experience and encapsulates the fact that you're using an API call to Auth0, which at the answer suggests, might change to being a cached representation in the future. Commented Dec 5, 2016 at 16:20
  • Thanks both for the well explained answer/comment. I'm still doubting between option 1 and 2. On first thought option 1 (Repository) will be better if there is need to join internal and Management API tables or that the Management API result needs more complex manipulation and option 2 (Web API) will be beter if the Management API results are mostly used straightaway without the need of manipulating (ex: show all users). I guess this will be different for all projects. Commented Dec 6, 2016 at 8:11
  • 1
    That choice is more difficult to get it right when looking from the outside without knowing all the little details of a specific project; In the end you should go with the one you feel most comfortable and is less complex. Since it's on the server-side, even if you get it wrong at first it's easier to refactor. Commented Dec 6, 2016 at 8:39