AJAX

Modern AJAX work commonly uses the Fetch API or related request interfaces. The returned data may be JSON, HTML, XML or another representation. In practical terms, AJAX belongs to the browser, server or document layer. Knowing that layer is important because it tells you what the term can change, what it cannot change, and where to look when something behaves unexpectedly.

The common mistake is to use AJAX as if it also meant API. That blurs two separate decisions and usually sends troubleshooting in the wrong direction. A better test is practical: Watch the Network panel while interacting with the page to confirm that background requests return the expected data.

In day-to-day work, AJAX matters when the concept needs to be identified precisely instead of being grouped with a nearby term. The practical value is not the vocabulary itself; it is being able to identify the right control, file, setting or decision when the concept becomes relevant.

A search box can fetch new results in the background and update only the results region instead of reloading the whole page. That example is useful because it turns the definition into something you can recognize, test and discuss with other people working on the same project.

Use these references when you need documentation-level detail, specifications or product-specific behavior beyond the plain-English explanation above.