arrow_back Securing your nodejs deployments while you sleep
Getting Up & Running with AngularJS arrow_forward
Managing API Resources and Their Relationships on the Front-end
Submitted by Himanshu Kapoor (@fleonus) on Wednesday, 6 August 2014
Section: Full talk Technical level: Intermediate
With the advent of Single Page Apps, a lot has changed in the world of web development. The days of server-side rendering are waning away, and the world is moving towards static HTML apps that communicate with a back-end API to drive the user experience.
Such transformation requires rapid communication between the Single Page App (front-end) and an API (back-end). This exchange of information brings about various challenges like maintaining consistency, optimizing for performance and scalability.
This talk would go over the challenges, we at Wingify, faced while making our Angular.js based Single Page App – Visual Website Optimizer. One of the core challenges is efficiently communicating with a back-end service. Finally, the talk would conclude with the solutions we came up with to tackle these problems.
This talk would detail problems faced with the seemingly trivial task of using Angular.js, to get and post data from a back-end API. I would go over these problems (questions) one by one, and propose a solution to them by providing relevant examples. These questions include:
- Fetching data from the server is as easy as making an AJAX request, but as the app logic becomes complex, how do you avoid making your codebase a tangled mess of AJAX requests?
- How do you ensure that multiple instances of the same resource are updated as soon as the resource is updated with the most up-to-date data, effectively maintaining a single source of truth across the app?
- How do you handle relationships between two resources? Fetching a resource could require fetching another child or related resource simultaneously; how would you go about instructing the app to do so?
- If you send a request to get something, how do you effectively cache its response so that you don’t have to send a request to fetch that resource again? How do you make sure that this storage mechanism performs well enough to return resources and sub-resources as quickly as possible?
- An app would involve several instances where the user inputs data that is posted to the server. How do you ensure only what the user changed is posted to the server, effectively making the payload as small as possible?
- The server might have its constraints when accepting data from the client. It could need some transformation before accepting a response. How would you serialize and transform this data before sending it to the server and still maintain consistency across the app?
- Similarly, such transformation might be necessary before receiving the response from the server. How do you make sure that request serialization and response unserialization works consistently?
The challenges listed above are based on real world problems we faced while developing version 3.0 of our website optimization software – Visual Website Optimizer. While solving some of the problems above, we abstracted out a lot of solutions to these problems into a service for Angular.js.