Paginating Through Server-Side Data


You wish to paginate through a large server-side result set.


You cannot use the previous method with a filter since that would require all data to be available on the client. Instead we use an implementation with a controller only instead.

The template has not changed much. Only the ng-repeat directive looks simpler now:

<tr ng-repeat="item in pagedItems">

In order to simplify the example we will fake a server-side service by providing an Angular service implementation for the items.

app.factory("Item", function() {

  var items = [];
  for (var i=0; i<50; i++) {
      id: i, name: "name "+ i, description: "description " + i

  return {
    get: function(offset, limit) {
      return items.slice(offset, offset+limit);
    total: function() {
      return items.length;

The service manages a list of items and has methods for retrieving a subset of items for a given offset and limit and the total number of items.

The controller uses dependency injection to access the Item service and contains almost the same methods as our previous recipe.

app.controller("PaginationCtrl", function($scope, Item) {

  $scope.itemsPerPage = 5;
  $scope.currentPage = 0;

  $scope.prevPage = function() {
    if ($scope.currentPage > 0) {

  $scope.prevPageDisabled = function() {
    return $scope.currentPage === 0 ? "disabled" : "";

  $scope.nextPage = function() {
    if ($scope.currentPage < $scope.pageCount() - 1) {

  $scope.nextPageDisabled = function() {
    return $scope.currentPage === $scope.pageCount() - 1 ? "disabled" : "";

  $scope.pageCount = function() {
    return Math.ceil($$scope.itemsPerPage);

  $scope.$watch("currentPage", function(newValue, oldValue) {
    $scope.pagedItems =
      Item.get(newValue*$scope.itemsPerPage, $scope.itemsPerPage);
    $ =;


You can find the complete example on github.


When you select the next/previous page you will change the $scope.currentPage value and the $watch function is triggered. It fetches fresh items for the current page and the total number of items. So, on the client side we only have five items available as defined in itemsPerPage and when paginating we throw away the items of the previous page and fetch new items.

If you want to try this with a real backend you only have to swap out the Item service implementation.