You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A API might have a good documentation and quick start guide, but API users would hardly use it if is slow to respond, doesn't have good number of successful API calls, etc. Using proxy's, we can always get this statistics and incorporate them in the API profile to measure DX. The main idea of evaluating the DX is about how consistent the API has been in maintaining its performances
Things to consider
Rate of successful API calls
number of users using the API
Deviation of time to respond (e.g. if a big file needs 10 sec, 2 mili second and 2 minutes to download - the response time is not consistent. Not good DX)
User Need
A API might have a good documentation and quick start guide, but API users would hardly use it if is slow to respond, doesn't have good number of successful API calls, etc. Using proxy's, we can always get this statistics and incorporate them in the API profile to measure DX. The main idea of evaluating the DX is about how consistent the API has been in maintaining its performances
Things to consider
Related Issue
#2452
The text was updated successfully, but these errors were encountered: