The Success of Embracing AngularJS in a Large-Scale Enterprise Solution

by Jeff Chew (@therealjeffchew) - Technology @Razorfish

On March 17th, I gave a talk at the Google office in Chelsea describing how to build a scalable AngularJS project. The magnitude of this kept with me for weeks leading up to this event, seeing that AngularJS is a JavaScript framework created by Google themselves. And looking at the roster, there were a couple of hundred people signed up to come, with an additional 200+ in the waiting list.

Rewind over a year ago, I joined the Ford account at Razorfish understanding that I’d be taking on and leading the Presentation Layer charge of a massive revamp of the Ford and Lincoln owner portals ( /

* *

* *

Its predecessors were on a platform called Fatwire, which the client has decided to leave on the wayside for a re-platform to the Adobe Experience Manager (AEM), an enterprise level content management system (CMS) by Adobe. Part of this revamp, we took the opportunity to reevaluate the performance and how we could make things better. Where it landed, we opted to separate all of the logic into various layers instead of letting the server side do all of the heavy lifting.

In the new stack, we are allowing AEM to do only what it does best, which is to deliver content. We then extracted all of the SOAP operations from the server side, and exposed those as a RESTful API layer that can communicate with the presentation layer. What this means is that all of the business logic now falls on the hands of the front-end.

We selected AngularJS as the framework of choice. In addition, we embraced AngularJS as a whole, and used it as a pure solution rather than a mix of other frameworks or libraries (i.e. jQuery, etc). This allowed us to fully utilize its unit testing capabilities, as well as the ability to fully modularize the product we are building. To elaborate on the idea of modularization, AngularJS gives the power to separate functionality into smaller pieces that can then be put together wherever those pieces are needed. For example, if we are creating a hook into the service layer, we only need to write it once then place it in any section that needs to use that hook. This particularly came in handy, as the number of RESTful service integration points reached close to 90 by the time the site launched.Extending the idea of modularization further, I was tasked with also architecting two projects that came in during the year; Ford’s corporate site (

Extending the idea of modularization further, I was tasked with also architecting two projects that came in during the year; Ford’s corporate site ( and another property owned by Ford called Quicklane (

* *

* *

Even though these sites had different business needs, I went with the same architectural structure as the Ford and Lincoln owner portals, then kicked off the respective development teams. What we noticed was that we saw a lot of commonality across the various work-streams. We didn’t think it made sense to reinvent things like an accordion, carousel, or even how we handle responsive imagery. We modularized all of these as standalone components, which we could then pick up and place from one work stream to another with minimal integration time.

The Ford corporate and Quicklane sites launched successfully in Q4 2014, while the owner portals launched without a hitch at the end of Q1 2015.

We also saw some considerable performance gains during our performance and load tests. Some highlights to note compared to the old Ford/Lincoln owner portals:

  • Login & Authenticated Homepage: 50% faster @ 9x load
  • Registration: 130% faster @ 3x load
  • Upload Software Installation Log: 328% faster @ 100x load
  • Check Sync Software Status: 536% faster @ 6x load

Part of the exploration of architecting a scalable AngularJS solution, I quickly realized that the approach we used was not documented or spoken of anywhere in the tech community. I took this as an opportunity to share how we were able to successfully leverage AngularJS on an enterprise solution across multiple work streams.

I prepared my presentation hot at the heels of the most recent launch, which wasn’t much time. On top of that, I was scheduled to do a dry run of the presentation with Google a day after the launch date. Fortunately, our launch went so smoothly it gave me time to start thinking around how I wanted to tell our story to Google and the tech community at large.

The final story evolved into two separate tales. One is how to guide a new AngularJS developer from a basic project, to something that is scalable and can be used in a real life project. This was told with multiple sample projects and building from a baseline to a usable product. The other story was the problem we were faced with, and how we applied this guide to the various Ford projects that are live today.

All in all, I’m proud of the work that the Razorfish Ford team was able to accomplish, and even prouder of the fact that we could tell our story outside the walls of our office. The presentation at Google was well received, and was delivered to a packed room with people standing in the back.

The presentation was recorded, and will be available on Google’s AngularJS Youtube channel in the near future.