A

Synopsis
on

Scaling of REST Services

submitted by
Utsav Dusad
Luv Varma
Ashwin Habbu
Shreya Tripathi

I. T. Department
Pune Institute of Computer Technology
University of Pune
2013-14

INTRODUCTION
REST services are playing a crucial role in building modern web application
and services. Good web application design involves several distributed components including one or more REST services backed by SQL and NO-SQL
data streams. Usually caching is done to serve contents over HTTP, so as to
scale the applications and the services provided by them seamlessly serving
up to billions of users at a time. However caching is conducive to static
data, but for dynamic data the contents need to be refreshed and served at
extremely fast speeds. REST has a major role to play in this. This project
deals with creating REST services that can serve these contents at extremely
fast speeds, without having to deal with any form of session management or
any other similar modules that are usually required for a full stack web application.

AIM
The aim of this project is to create a REST service deployed using a new
or custom micro web server and/or framework where it should support only
REST features. By doing this we want to be able to make the service scalable according to the application and serve any number of customers at an
extremely high speed . This service will be customized for GET messages
only.

OBJECTIVE
There are a number of other protocols built on top of HTTP, that are designed
to specifically build web services. They focus on using HTTP as a transport
protocol for enormous XML encoded messages. The resulting service is very
complex, almost impossible to debug and wont work unless the clients also
have the exact same setup. The main issue with this is that the HTTP
is used as a means of sending the XML encoded data when HTTP can be
used to send the contents as it is. RESTful web services require none of
this internal complexity, and therefore it can instead spend its complexity
on additional features or on making multiple services interact. We want to
create or customise a web framework that will deploy a RESTful web service
that will be lightweight, scalable and serve the Clients at a super fast speed.
However it will be customized for GET messages only.
3

LITERATURE SURVEY

Survey

In this paper, brief introductions of RPC and REST are provided. Then
two kinds of architectural styles are analyzed and compared from the perspectives of scalability, coupling, and security. RCAT: a RESTful Clientscalable ArchiTecture-Thomas Debeauvais, Arthur Valadares, Cristina V.
Lopes.School of Information and Computer Science,University of California. This paper presents a system architecture abiding to the constraints
of the REpresentational State Transfer (REST) architectural style. This architecture divides the resource requirements into separate layers and suggests
how they can be addressed efficiently in isolation. Towards Property-Based
Testing of RESTful Web Services-Pablo Lamela Seijas.University of Kent,
Huiqing Li.University of Kent, Simon Thompson;University of Kent. In this
paper, as a first step towards automating the testing of Web Services over
HTTP, we describe a practicalmechanism and model for testing RESTful
Web Services without side effects and give an example of how we successfully
adapted that mechanism to test two different existing Web Services:Storage
Room by Thriventures and GoogleTasks by Google. RESTful Web ServicesLeonard Richardson and Sam Ruby This book talks about principles underlying the Web: Representational State Transfer, or REST. It introduce the
Resource-Oriented Architecture (ROA), a commonsense set of rules for designing RESTful web services. It also shows the view from the client side:
how you can write programs to consume RESTful services.

PROBLEM STATEMENT
We want to imagine and design a REST service deployed using a new or
custom micro web server and/or framework where it should support only
REST only features. No session management and any other similar module
that usually required for a full stack web application. We will target only
GET requests.

PROJECT PLAN
Months 1, 2, 3: Study of various web service protocols and architectures
such as HTTP, SOAP, REST architecture, MVC architecture, Advantages
of REST etc. More focused on understanding the importance of REST architecture Month 4: Development of RESTful web services on various web
frameworks. Analysis of these services will be carried out and performance
measured. The different modules of a micro web server or framework will
also be examined. Month 5: Development of a testing environment where
the perfomance of each service is measured and generated. Implementation
will also begin in the form of customising framework modules and compiling
and implementing them. Months 6, 7: Implementation of the RESTful architecture by customising a web framework. Show how the RESTful server
is more efficient than the other servers. Also highlight the performance before/after the customization, how the change was brought about and what
was actually changed. Main focus will be on which HTTP and Web Server
factors were responsible for making the Web Server efficient enough.

PROJECT METHODOLOGY
Initially we will study various micro web frameworks and pick one based on
its features. We will study its modules and begin customizing them as per our
requirements. A testing environment will be created where the modules will
be compiled and tested after the customization. Several different concurrent
RESTful services will also be tested and the resultant report (consisting of
response time and number of concurrent services) will be generated. We want
to showcase how a RESTful server is more efficient than the others and on
what HTTP and Web Service factors is the performance dependant.

EXPECTED OUTCOME
A RESTful Web Server that is both lightweight and extremely fast. It will
service only GET requests. The server will be customized as per the requirements and the factors on which the efficiency is dependant will be highlighted.

A
Synopsis
on

Scaling of REST Services

submitted by
Ashwin Habbu
Luv Varma
Shreya Tripathi
Utsav Dusad
Mr. S. S. Pande
Guide

Mr.S.B.Deshmukh
Project Co-ordinator

Dr.Emmanuel.M.
HoD.

REFERENCES

References

[ 1]RESTful Client-scalable ArchiTecture-Thomas Debeauvais, Arthur Valadares, Cristina V. Lopes.School of Information and Computer Science,University
of California.
[ 2]Towards Property-Based Testing of RESTful Web Services-Pablo Lamela
Seijas;University of Kent, Huiqing Li.University of Kent, Simon Thompson;University of Kent. ]
[ 3]RESTful Web Services-Leonard Richardson and Sam Ruby.

10