Can AngularJS auto-update a view if a persistent model (server database) is changed by an external app?

I'm just starting to familiarize with AngularJS, but I would like to build a web app that has a view that gets auto-upated in real-time (no refresh) for the user when something changes in the server-side database.

Can AngularJS handle this (mostly) automatically for me? And if so, what is the basic mechanism at work?

For example, do you somehow setup AngularJS to poll the DB regularly for "model" changes? Or use some sort of Comet-like mechanism to notify AngularJS client-side code that the model has changed?

In my application, the challenge is that other (non-web) server-side software will be updating the database at times. But this question applies equally to pure web-apps where you might have multiple clients changing the database through AngularJS web clients, and they each need to be updated when one of them makes a change to the DB (model).



You have a few choices...

  1. You could do polling every X milliseconds using $timeout and $http, or if the data you're using is hooked up to a REST service, you could use $resource instead of $http.

  2. You could create a service that uses some Websocket implementation and uses scope.$apply to handle changes that are pushed by the socket. Here's an example using, a node.js websocket library:

    myApp.factory('Socket', function($rootScope) {
        var socket = io.connect('http://localhost:3000');
        //Override socket.on to $apply the changes to angular
        return {
            on: function(eventName, fn) {
                socket.on(eventName, function(data) {
                    $rootScope.$apply(function() {
            emit: socket.emit
    function MyCtrl($scope, Socket) {
        Socket.on('content:changed', function(data) {
            $ = data;
        $scope.submitContent = function() {
            socket.emit('content:changed', $;
  3. You could get really high tech and create a websocket implementation which syncs an Angular model with the server. When the client changes something, that change gets automatically sent to the server. Or if the server changes, it gets sent to the client.
    Here's an example of that in an old version of Angular, again using

EDIT: For #3, I've been using Firebase to do this.


Here's an implementation that uses jetty instead node. The angularjs part is based on the angular-seed app. I'm not sure if the angular code is idiomatic...but I've tested that this works. HTH -Todd.

TimerWebSocketServlet see


// -------------------------------------------------------------
// TimerCtrl
// -------------------------------------------------------------
function TimerCtrl($scope, CurrentTime) {
    $scope.CurrentTime = CurrentTime;
        function (m) {
            console.log("message invoked in CurrentTimeCB: " + m);
                $scope.currentTime =;
TimerCtrl.$inject = ['$scope', 'CurrentTime'];


angular.module('TimerService', [], function ($provide) {
    $provide.factory('CurrentTime', function () {
        var onOpenCB, onCloseCB, onMessageCB;
        var location = "ws://localhost:8888/api/timer"
        var ws = new WebSocket(location);
        ws.onopen = function () {
            if(onOpenCB !== undefined)
        ws.onclose = function () {
            if(onCloseCB !== undefined)
        ws.onmessage = function (m) {

            setOnOpenCB: function(cb){
               onOpenCB = cb;
            setOnCloseCB: function(cb){
                onCloseCB = cb;
            setOnMessageCB: function(cb){
                onMessageCB = cb;



What you are looking for is Firebase and Deployd. Firebase comes with an adapter too that makes using it a breeze:


According to the "Discover Meteor" book, Angular watches/scopes are similar to Meteor's computations regarding reactivity... but Angular is client-only and gives less-granular control than Meteor.

My impression is that using Angular might be a better fit for adding reactivity to an existing app, whereas Meteor soars when you use it for the whole thing. But I have no real experience with Angular yet (though I have built some small Meteor apps).


So, Andy Joslin has mentioned the best solution in my opnion in his answer, the 3rd option, which is to maintain state bidirectionally via websockets or whatever other async library you're dealing with (this would be the Chrome message API for Chrome Extensions and Apps for instance), and toddg has given an example of how that would be achieved. However, in his example he is implementing an anti-pattern in AngularJS: the service is calling the controller. Instead, the model should be placed inside the service, and then referenced from the controller.

The service socket callbacks will modify the service model, and because it is referenced from the controller, it will update the view. Careful if you're dealing with primitive data types or variables that can be reassigned though, those will need a watch on the controller to make this work.


Recent Questions

Top Questions

Home Tags Terms of Service Privacy Policy DMCA Contact Us

©2020 All rights reserved.