Deferred and promise are part of jQuery since version 1.5 and they help in handling asynchronous functions like Ajax.

Long before Facebook and Xbox, If you wanted to catch a mouseclick, you did it with element.onclick = someFunction; This became a problem when another part of the code also wanted to listen to this click. This was not possible, because you could only assign one function. This was solved at the time with the addEventListener DOM function. With this, you can add as many listener functions as you want. Since then, that’s the way we know how to do this.

Now we have a similar problem with Ajax calls. This time it’s not the events, but the fact that Ajax supports only one callback function. Not only the jQuery $.ajax() call, but also the underlying XMLHttpRequest object.


Until jQuery 1.5, a typical $.ajax() call looked like this:

  url: "/myServerScript",
  success: mySuccessFunction,
  error: myErrorFunction

The $.ajax() call returns a jQuery XMLHttpRequest object. Nothing new so far.

Since version 1.5, the returned object implements the CommonJS Promises/A interface. That’s a mouth full. CommonJS is a initiative to define common and independent interfaces (API’s). Promises/A is one such interface. The advantage is that these are not jQuery specific. For example, if you work with Node.js, there is a good chance you’ll program with this same interface. That’s good.

The way of assigning callbacks with Promises is quite different:

var promise = $.ajax({
  url: "/myServerScript"


You can combine the done() and fail() functions in one then() function. The code above can be rewritten as:

var promise = $.ajax({
  url: "/myServerScript"

promise.then(mySuccessFunction, myErrorFunction);

Okay, the interface has changed, so what’s in it for me?, you might ask.

The advantages of promises are:

1) You can call the done() and fail() functions more times, with different callbacks. Maybe you have a callback function that stops an animation, one that does a new Ajax call and another function that shows the received data to the visitor.

var promise = $.ajax({
  url: "/myServerScript"


2) Even after the Ajax call has finished, you can still call the done() and fail() functions and the callbacks are executed immediately. So no messing around with variables holding different states. When an Ajax call has finished, it will end up in either the success state or the failed state and this state will not change.

3) You can combine promises. Sometimes you need to do two simultaneous Ajax calls and you want to execute a function when both are successfully finished. To do this, you use the new $.when() function.

var promise1 = $.ajax("/myServerScript1");
var promise2 = $.ajax("/myServerScript2");

$.when(promise1, promise2).done(function(xhrObject1, xhrObject2) {
  // Handle both XHR objects

In contrast to what you might expect, the callback functions don’t get the received data as arguments, but the XHR objects. For Ajax requests this is very useful, but if you want to use $.when for other asynchronous code, it will be much harder.

4) Since jQuery 1.8, you can chain the then() function sequentially. In the code below, first promise1 is run and when resolved successfully, getStuff is run, returning a promise and when this is resolved successfully, the anonymous function is executed.

var promise1 = $.ajax("/myServerScript1");

function getStuff() {
    return $.ajax("/myServerScript2");

  // Both promises are resolved

Every callback function receives the result of the previous asynchronous function, in the case of Ajax, that would be the returned data.


So what is a deferred and what is the difference with a promise? As you have seen above, a promise is an object that is returned from an asynchronous function. You need a deferred when you write such a function yourself.

A deferred object can do the same as a promise object, but it has two functions to trigger the done() and fail() functions.

A deferred object has a resolve() functions for a successful result and to execute the functions assigned with done(). The reject() function is for a failed result and executes the functions assigned with fail().

You can give parameters to both the resolve() and reject() functions and they will be passed on to the functions registered with done() and fail().

The promise object does not have resolve() or reject() functions. This is because you give the promise away to other scripts and you don’t want them to resolve or reject the promise.

Below is a simple script that illustrates how it works. The html is just an empty div with id result.


var promise = wait();

function result() {

function wait() {
  var deferred = $.Deferred();

  setTimeout(function() {
  }, 2000);

  return deferred.promise();

You can also find this script on jsFiddle, so that you can experiment with it yourself.

The wait() function is the function returning a promise. This will be resolved with a setTimeout of two seconds. Instead of setTimeout, everything can be used that is asynchronous, like animations, Web workers etcetera. It should be clear that inside the wait() function, we use the deferred object, but we return the limited promise object.


Domenic Denicola wrote the article You’re Missing the Point of Promises in which he criticizes jQuery’s implementation of Promises.

Take for example the following code:

promise.then(fn1).then(fn2).then(fn3, fail);

If an error is thrown in fn1, the fail function should be called. This is a very nice way to handle errors in asynchronous functions. This does not work in jQuery and the writer sees this as a major shortcoming of jQuery.

If you want to use pure Promises/A, there are several JavaScript libraries to choose from. For example Q by Kristopher Kowal.

This is an article about deferred and promise in jQuery.