Building SPA Using Node.js and AngularJS
Web application development is as fickle as any other facet of development; one year’s standards are next year’s artifacts. A fairly new approach to web application development is the creation of single page applications (SPA), in which the web application is contained on a single web page that operates asynchronously in real-time. CRUD operations, workflows, and state management all take place on the page, and these can be initiated by either the server or the client using AJAX.
Single page applications tend to have the feel of a native application. There are no refreshes, and the interface displays real-time information. Even more exciting is the ongoing functionality of the application even if the user loses connection, since most of the page is cached.
Why use Node.js?
This doesn’t translate to Node being the best thing the world has ever seen, barring sliced bread. Node shouldn’t be used for CPU intensive operations, but instead for high-throughput applications that need to be fast and scalable.
Speed is one of the main perks of Node. It uses a single thread event loop that performs all operations asynchronously. When an application using Node needs to perform an operation, it sends it to the event loop with a callback function attached, and then keeps on keepin’ on until the event loop returns to the task that sent the callback.
Why use AngularJS?
Data binding support is provided using directives included with AngularJS. This means the support for data model synchronization in real-time is built in. All changes to the view or the data model are automatically reflected. These features make using AngularJS for a single page application almost a no-brainer.
Originally published at axiom88.com.