21 Four Web 2.0 technologies (SOAP/REST/AJAX/MASHUP)

Dear students,

We start our Unit 3 with one of cloud technologies Web 2.0

When internet was born, lot of applications that were created could be termed as Web 1.0. Then Web 2.0 technology enhanced the Web technologies.

Web 2.0 covered four different technologies namely

  1. SOAP services
  2. REST services
  3. AJAX services
  4. MASHUP services

We covered the entire Semester 2 learning about SOAP services and REST services

SOAP Services

SOAP services utilized SOAP protocol 1.0, 1.1, 1.2. It initially operated using HTTP, was inter-operable between any type of systems, languages, applications. SOAP made application integration easier and was loosely coupled. SOAP utilized XML data structure for any type of communication over HTTP application protocol. SOAP now works on protocol other than HTTP too and is suitable for complex applications.

REST services

REST services later was introduced to be much simpler that worked in distributed system with simple URI links and plain HTTP CRUD methods (GET/POST/PUT/DELETE). REST introduced JSON data structures which was easier to understand , use and much faster to operate on, compared to XML. REST is a good candidate for HTTP based applications.

AJAX

In earlier days, javascript was mainly responsible only for front end web page. AJAX enabled multitasking of web page. AJAX introduced backend processing multiplexed with front end processing. Just like an operating system multitasks giving user a richer experience of using multiple applications, AJAX uses controllers, event listeners model within javascript to make back end server tasks when the network is idle, while page is busy.

While one javascript function could collect data from back end, it would operate asynchronously not to stop the web page from performing any of its front end page functionality. AJAX stands for Asynchronous Javascript and XML

Java script works on single thread on a page and hence AJAX is not multithreaded but supports multitasking. But the browser can create multiple threads as it is a desktop application which has lot more permissions to create new threads, read and write to file, create more network connections etc.

MASHUP

While AJAX could connect from front end to back end without interrupting any of the processes running on a web page, MASHUP could bring together different back end services and do the needful to present/display it on the web page . The mashup reduces programmers effort to create a front end screen for the back end services it uses.

The best example of MASHUP is where with few lines of code in HTML, we can add and display a Google map with all its complex functionality without having to worry about writing the code to manage the map functionality on the page. The MASHUP code as such internally would be accessing varied services using the other Web 2.0 technologies like AJAX, REST or SOAP, thereby hiding all complexity to call the services or present it on the web page.

Lot of front end javascript frameworks like JQuery, AngularJS, NodeJS etc. support Web 2.0 technologies.

Web 2.0 helped developers to create rich internet applications (RIA)

For more details, have a look at presentation 1 / presentation 2.

Thank you.

Comments

Post a Comment

Popular posts from this blog

11 Computing Platforms

Welcome students ! Introduction to Unit 2  In Unit 2, we look at platform architectures that have evolved over time from the days of  earlier main frame architecture into today's cloud service platform architecture. Today we have cloud computing platform which use and provide cloud technologies   ( Parallel Computing, Distributed Computing, Service Oriented     Computing, Virtualization, Web 2.0 (soap, rest, ajax, mashup),  Utility Computing ) cloud delivery services reference model  ( IaaS,PaaS, SaaS ) cloud deployment types  ( Public, Private, Hybrid, Community ) In Unit 1 we already introduced ourselves to cloud technologies such as Parallel Computing, Distributed Computing, Service Oriented Computing and Virtualization.  Just like evolution theory says a monkey became man over many phases, this blog summarizes the Computing Platform architecture for enterprises that has evolved over time in four phases  (computing platform: e...
Read more

15 Four layers of Cloud Architecture (Reference Model)

Hello students, In today's blog we look deeper at cloud reference model architecture that generally applies in any cloud environment Any Cloud architecture is based on a four layers of this reference model 1. System Infrastructure 2. Core Middleware 3. User-level Middleware 4. Cloud Applications Each layer is on top of the previous layer System Infrastructure System infrastructure is the most underlying layer in the architecture and it provides physical machines, network, storage needs such as network adapters, routers, SAN disks etc. Core Middleware Core Middleware sits on top of System Infrastructure layer. It provides virtual machines, network virtualization, storage virtualization, hypervisors etc. Both System Infrastructure and Core Middleware essentially provides a way to implement IaaS (Infrastructure as a service) In our assignment, this layer would ideally be Oracle Virtual box User Level Middleware User Level Middleware sits on top of core middleware and provides run-ti...
Read more

25 Task Computing : HTC-HPC-MTC

Dear students, In our last blog, we came across concurrent computing, where the focus was how a single program can be computed faster by decomposing either based on data sets (Domain Decomposition) or based on functionality (Function Decomposition). Once the decomposition is planned properly in the program, it can be assigned to multiple cores or multiple threads. Concurrent computing is a form of parallelism on the same machine. When we talk about task computing, we are looking at executing not single program, but multiple programs. Each program can be considered as a task with lot of data or consisting of many work units. These tasks can be executed using multiple machines. Task Computing is a form of parallelism on multiple machines. It is a network of machines, where one machine (called local node) becomes responsible to submit the task, then one machine schedules it , checks status on all submitted tasks (access nodes) , one machine provides any resources such as files, data...
Read more