International Research Journal of Engineering and Technology (IRJET) e-ISSN: 2395-0056
Volume: 07 Issue: 05 | May 2020 www.irjet.net p-ISSN: 2395-0072
© 2020, IRJET | Impact Factor value: 7.529 | ISO 9001:2008 Certified Journal | Page 7613
An Interpretation and Anatomization of Angular: A Google Web
Framework
Anirudh Bhaskar
1
, Manjunath A.E
2
1
B.E. Department of Computer Science and Engineering, R.V. College of Engineering
2
Assistant Professor, Department of Computer Science and Engineering, R.V. College of Engineering
---------------------------------------------------------------------***---------------------------------------------------------------------
Abstract - With the rapid advancement in technology and more focus being emphasised upon user satisfaction, it is vital for
various web application frameworks to constantly keep themselves updated in order to meet the needs of the current market. With
a plethora of web frameworks available, it is essential that the developer chooses the correct framework. In this paper, a detailed
analysis of the origin, history, features and advantages of the Google produced framework, called Angular is investigated. Along
with this, a discussion as to why Angular is preferred for Single Page Applications is also given.
Key Words: Angular, Single Page Applications, Web frameworks, HTML, TypeScript, Client side and Server Side routing.
1.INTRODUCTION
A couple of years before its initial release, a Google employee going by the name of Miško Hevery, created a famous web
framework called AngularJS used solely for internal purposes. The purpose of AngularJS was to build appealing web
applications for the several projects Miško was working on. However a few years later, in the year of 2010, a team spearheaded
by Miško started making web applications using AngularJS. It was then decided to release AngularJS as an open source software
which will be available to the public thereby enabling everyone to make fluid web applications. Half a decade later, with various
advancements in JavaScript and the release of newer and faster frameworks such as React caused many problems for
AngularJS. AngularJS was just a small project that was created at google for building simple web applications. It was not able to
cope up with the demands of large enterprise applications thereby causing it to go obsolete. The core team at Google went on to
take an executive decision and write a brand-new framework from the ground up and it was called Angular 2(called “Angular”
nowadays). The first release of Angular 2 was released on 14
th
September 2016. In this paper, an in-depth analysis of Angular is
carried out.
2. SINGLE PAGE APPLICATIONS
Before diving into the details of Angular, it is important for one to know what a Single Page Application(SPA) is. In [1], an SPA is
defined as a web application which is comprised of many individual components and these components can be replaced
independently thereby preventing the entire web page to reload upon a user action.
In the olden days there were a plethora of HTML files which were interlinked and upon every user action the web page used to
reload and go to the respective HTML file. This took a lot of time, and the end users were left dissatisfied.
The next question that arises is that, how do we implement SPA’s? The answer is simple. We make use of the concept of client
side routing. Client side routing is a type of routing in which when a user carries out an action, at any given instance the full
webpage will not be reloaded. Instead, JavaScript or TypeScript will update the URL and then display the required content.
One must keep in mind; Angular can be used to build a variety of applications. Single Page Applications just happens to be one
of the more famous applications used in the world today.