Frequently asked questions
ArcGIS REST JS
The ArcGIS API for JavaScript provides many of the same tools as ArcGIS REST JS. However, there are some key differences.
| Pros | Cons |
|---|---|
| Full mapping library | Larger, slower builds |
| Support for a wide variety of services | Not fully supported in Node JS |
| Support for additional authentication options | Less methods for portal operations |
| Includes geometry engine |
In general, if you are displaying and visualizing data on a map in a browser use the ArcGIS API for JavaScript. If you are building a non-mapping application, consider ArcGIS REST JS.
ArcGIS REST JS attempts for as few tradeoffs as possible over making requests with tools like fetch. ArcGIS REST JS automatically handles proper parameter encoding for ArcGIS REST APIs, has error handling, token management and more.
Before tree shaking, all of this logic is ~8kb. Additional methods are around 1kb each or less, making the cost of adding ArcGIS REST JS to your application low.
You can go to the ArcGIS REST JS Github Repository.
Resources
You can visit the Mapping APIs and services guide.
You can go to the Glossary.
Visit the Deployment chapter in the Mapping APIs and location services guide.