Amazon-Fresh-Project-Report (1)

AMAZON FARMERS FRESH
1 | P a g e
CMPE 273 Group Project
Spring 2016
CMPE273 – Enterprise DistributedSystems
FINAL GROUP REPORT
On
Amazon Market Fresh
Instructor:
Dr. Simon Shim
Submission Date: SubmittedBy:
May 1, 2016 Dhiraj Gurnani
Satyateja Pothuru
AshwiniChellagurki
Vimal Muraleedharan Nair
Vaishampayan Reddy Pathuri

2 | P a g e
INDEX
1. Introduction: stateyour goals, purposeof system. .............................. 3
2. System Design: Describeyour chosen system design. ...........................3
3. ObjectManagement Policy..................................................................8
3.1 Planning and Requirement Analysis. ...............................................8
3.2 Consideration of theFunctional Requirements............................... 8
3.3 Development. ...............................................................................9
3.4 Testing theSystem. ........................................................................9
4. Handling of Heavy WeightResources. .................................................. 9
4.1 Usage of Connection Pooling. ........................................................ 9
4.2 Usage of Rabbit MQ. ..................................................................... 10
4.3 Usage of Redis Caching.................................................................. 11
5. Policy used to decide when to writeto data.......................................... 12
6. Implementation Details: Performance/Mocha Tests............................. 12
7. Use Cases/Work Flow–Screenshots… ................................................. 16
8. Dynamic Pricing Algorithm… ................................................................ 43

3 | P a g e
1. Introduction:
The goal of our system is to develop an application which is similar to AmazonFresh
Farmers Marketto demostrate the useof REST based Web Services in our Middleware
technology , the use of RabbitMQ as a messaging platformfor communication between
front-end channels with backend systems, and implementing the connection pooling
concept to effectively manage our connections and how it effects the overall
performanceof the system and finally to showcaseas to where and which pages to use
the SQL and NOSQL databasein our system. Our Application offers widerangeof
grocery items for sale, as well as a subsetof items for purchaseto the customers.Items
that are ordered are available for home delivery on the sameday or the next day,
depending on the time of the order and the availability of trucks which arealso
managed by our application.Herethe local farmers can sell their fresh producesuch as
lettuce, tomato, potato, oranges,carrots,etc to customersbygetting them approvedby
the admin. The farmers puttheir descriptions of products and introduction to their
farms that includes history, farming methods, video tour,owner profileetc. Customers
can browsemany local farmers and items, and makepurchases.They can check the
order progress in the web and also check the real time locatin of the delivery truck
through googlemaps.
2. SystemDesign:
Block Diagram for AmazonFresh

4 | P a g e
Schema Diagram:
Mongo DB:

5 | P a g e
Sessions (Implementedusing Passport.JS andstoredinMongo)
SystemDesign(Continued….)
Amazon Fresh Client represents the front-end wherecustomers can select various
agricultural items fromdifferent forms. Functionality such as available fresh produce
items, delivery method and description of farmers and forming methods can be
accessed fromthis page. User interface is customized for the role of the logged in user.
If the logged in user is a customer and if the request is made to buy a productthen
server enques this in a request queue with a specific correlation_id. This requestwill be
forther forwarded to service defined for this type of request. Itis here RabbitMQ plays

6 | P a g e
an important role of decoupling the different components to address scalability. After
the requesthas been serviced, the responsewill be enqueued in the RabbitMQ
responsequeue for the predefined correlation_id. Finally, it will be sent back to client
for display. All the session level and configuration information is stored in the Redis
cache. Oncethe user is authenticated, for the subsequentrequests the information
stored in the Redis cache will be retrived for the validation.
In our AmazonFresh Farmers Marketapplication, weare making use of bootstrap,
HTML5 and angularjs for the client side code and Node js for the server sidecode. The
application provides the users with a AmazonFresh Farmers Market likeinterfacewith
the basic functionalities likeallowing the farmer to sell his fresh produceby creating his
accountand by updating his products which arein prior approved by the admin and are
purchased by the customers who can view all the products, ratethemand review them
and are also provided with information about a registered delivery truck and can live
track it while it is out for delivery.Thecustomers arealso provided with a bill at the end
of each order placed.The products are also dynamically priced with their price varying
on the days when they havehigh demand etc. The customer should be logged in while
doing a checkoutof the products , if not he can signup and carry outthe request. The
farmer,customer,admin product, trucks and billing information is stored in Mysqland is
retrieved whenever required whereas the farmer introduction video and all images are
stored in MongoDb for easy management.Wehavemadeuse of connection pooling in
the databaseto effectively manageour connections and to not create a overhead on
the system as wewill be testing our application on huge data. Wehavemade useof
RabbitMq as a messaging platform for high availability and to increase the
performance.
Test Scenarios:
We have also used testing frameworks to test our application namely Jmeter for testing
the performanceof the systemwhen subjected to varying load of the clients and the
other namely mocha testing framework.
Github:
We have used GitHub which is a web-based Git repository to host our Application.
URL: https://github.com/vaisham92/AmazonFreshMock

7 | P a g e

8 | P a g e
3.Object ManagementPolicy
3.1 Planning and Requirement Analysis:
In this stage, we analyzed and performed requirement analysis, as per the project
requirements in the three tiers which are as follows:
a) The client tier: The front-end users namely customers, farmersand theadmin will
interact with our applications and sends responses using theUI interface.
b) The middle tier/middleware: The majority of the processing of the inputs takesplace
in this tier, it performs the sending and receiving of the messages between distributed
systems. Itis atthis most critical point that it needs to integratenew components or to
scaleexisting ones as efficiently as possible.Themodules havebeen implemented using
RabbitMQ which implements the Advanced Message QueuingProtocol.
c) The third tier: This tier consists of database to storedata of the system. Atthis tier,
we also have constraints and relations that define the data. Mostof the modules use
MySQL as the relational databaseand the videos and images are stored using MongoDB
as the NoSQL database to storedata.
3.2 Considerationof the Functional Requirements:
As per the projectrequirement, we implemented different modules namely Farmers,
Customers, Billing, Admin, Billing and Trucks. Each of the modules have an associated
schema which are responsiblefor showing how objectshould be stored in database.
Each objects exhibits their respectivefunctionalities as per the projectrequirements.
3.3 Development:
According to the projectrequirement, we havecreated the UI and have implemented
differentfunctionalities. Additionaly, Wehave also implemented key features likemaps
using Google maps API and live tracking of the trucks by the customer track the exact
location of the truck.Wehaveused connection pool to efftectively manage our
connections on huge load and Rabbit MQ to increasethe sustainability while the load
in high.

9 | P a g e
3.4 Testing the System:
After the development of our application, on the basis of requirement, we haveused
testing frameworks to test our application namely Jmeter for testing the performance
of the system when subjected to varying load of the clients and the other namely
mocha testing framework.Wehavealso drafted the test cases which were checked if all
the requirement functionality is working fine or not.
4. Handling of Heavy WeightResources
We have used the following to efficiently manage the heavy weight resources :
4.1 Usage of ConnectionPooling:
Whenever an application needs an access to databaseit connects to the database.
Hence, it will be disadvantageous if it connects every time a user sends a requestfor a
particular data.so our application makes useof connection pooling wherewe maintain
a pool of connection instances.Herewecan create any number of connection objects
and keep it in a pool so if a requestcomes it will take a instance fromthe pool and
serve. After accessing the data and we no longer want the connection werelease it
back into the pool and it will be reused by some other function.In this way, it makes the
access faster improves the performanceof an application.

10 | P a g e
4.2 Usage of Rabbit MQ
Rabbit MQ is a messagepassing servicewhich uses the AMQP protocol. It serves
request fromclient to server and sends responsefromserver to client. Messaging
enables softwareapplications to connect and scale. We have made separate queues for
handling the data fromdifferent modules viz. admin, truck,farmers,productcustomer,
billing etc. Applications can connect to each other, as components of a larger
application, or to user devices and data. Messaging is asynchronous, decoupling
applications by separating sending and receiving data.Hence by making use of
RabbitMQ in our systemweare making it reliable and highly available.

11 | P a g e
4.3 Usage of RedisCaching:
Redis is a remote data structureserver and is extremely useful for cache management.
Redis can be accessed by all the processes of your applications, possibly running on
severalnodes (something local memory cannot achieve). Redis memory storageis quite
efficient, and done in a separateprocess. If theapplication runs on a platform whose
memory is garbagecollected (node.js, java, etc ...), it allows handling a much bigger
memory cache/store. Redis can also persistthe data on disk if needed. Redis can
replicate its activity with a master/slavemechanismin order to implement high-
availability. Itallows for fine-grained control over eviction though a choice of six
different eviction policies. Redis employs more sophisticated approaches to memory
management and eviction candidate selection. Redis gives us much greater flexibility
regarding the objects we can cache. Redis allows key names and values to be as large as
512MBeach, and they are binary safe. Redis has six data types that enable more
intelligent caching and manipulation of cached data, opening up a world of possibilities
to the application developer.Hence By making use of Redis in our application we are
making it highly available and efficient.

12 | P a g e
5. Policy used to decide when to write todata
In our application we havewriten or haveupdated into our database only after the
processing of our requestis complete so that the data inserted into the database is
correct and notincomplete.
6. IMPLEMENTATION DETAILS
1. Performance TestingUpdates

13 | P a g e
Note: Performed on heaviest call – getBillDetails
ResponseTime
25
20
15
10
5
0
100 200 300 400 500 1000
Number of Concurrent Users
Without Connection Pooling With Connection Pooling
Rabbit MQ + Connection Pool Rabbit MQ + ConnectionPool + Redis
Numberofestimatedtransactions/sec

14 | P a g e
2. Mocha TestCases:
Performanceimprovement VsConcurrency
45%
40%
35%
30%
25%
20%
15%
10%
5%
0%
100 200 300 400 500 1000
Concurrency
Connection Pool ConnectionPool + Rabbit MQ ConnectionPool + Rabbit MQ + RedisCache
PeformanceImprovementin%

15 | P a g e
Source Code for Mocha test cases:
describe('http tests', function(){
it('Location Statistics API', function(done){
http.get('http://localhost:3000/api/admin/trips/locationStats',
function(res) {
})
});
assert.equal(200,res.statusCode);
done();
it('Revenue Statistics API', function(done){
http.get('http://localhost:3000/api/admin/trips/revenueStats',
function(res) {
})
});
done();
it('Get PassportSession', function(done){
http.get('http://localhost:3000/api/getSessionInfo', function(res) {
done();
})
});
it('Get Pending Trips', function(done){
http.get('http://localhost:3000/api/admin/trips/getPendingTrips',
function(res) {
})
});
done();
it('Get Bills', function(done){
http.get('http://localhost:3000/api/admin/trips/getBills', function(res) {
done();
})
});

16 | P a g e
});
7. Use Cases/UI FlowsScreenshots.
 Welcome Page
 Click Signin

17 | P a g e
 Register User (Customer andfarmer)
 Validating the fields in Sign uppage

18 | P a g e

19 | P a g e
 Password Encryption(AESAlgorithm)
 Now Approvethe farmer through AdminPage.

20 | P a g e
 Enter Admin Details
 Logging in as Admin

21 | P a g e
 Go to Farmer ApprovalPage
 ApprovetheFarmer

22 | P a g e
 Approved andLogout
 Admin Tracking

23 | P a g e
 Now checking the Login Functionality

24 | P a g e
 View the Farmer Welcome Page& click on edit farmerprofile

25 | P a g e
 Updated farmerprofile
 Click new productin homepage and add newproduct(Apple)

26 | P a g e
 The new productcreated
 Logging in as admin

27 | P a g e
 Creating trips
 Checking pending trips

28 | P a g e
 Checking tripstatistics
 Checking Revenuestatistics

29 | P a g e
 Checking all bills placed
 Approving a farmer

30 | P a g e
 Approving a product
 Viewing dynamicpricing

31 | P a g e
 Entering the price with referenceto dynamic price &updating
 Signing in with customer

32 | P a g e
 Entering zipcodes
 Editing Customerprofile
 Click Edit

33 | P a g e
 Home page part-1

34 | P a g e
 Part-2
 Clicking the fruits subcategory

35 | P a g e
 Clicking the apples productcategory
 Clicking the specific apple (Product)
 Searching a product

36 | P a g e
 FarmerProducts

37 | P a g e
 ProductsInformationPagewith ratingsand review

38 | P a g e
 Inserting Rating (1 Star, 2 Star,3 Star, 4 Star,5 Star)

39 | P a g e

40 | P a g e
 Adding Reviews andratings

41 | P a g e
 Showing averageratings

42 | P a g e
 CartInformation
 Getting Farmer Details on the Cartpage.

43 | P a g e
 Looking at the reviews in the productpage

44 | P a g e
 Cart page after adding producttocart
 Clicki proceed to checkout and filling shippingdetails

45 | P a g e
 Clicking continue and going to payment infopage
 Click pay now and going to confirmationpage

46 | P a g e
 Clicking profilebutton
 Profileview

47 | P a g e
 Clicking all placed orders
 View placed orders

48 | P a g e
 Signing out
 Back to login page

49 | P a g e
8. Dynamic PricingAlgorithm.
 Compute the averagepriceof the same productfor all quantity in the Database.
 Compute the averagepriceof the same productsold by the AmazonFresh.
 Then find the averageof step1 and step2 in the databasewhich will shown as the
dynamic price based on demand supplymodel.
 If no similar products are available, DPA will show the result asnull.
 The admin has an option to enter the price fromthe DFAAlgorithm.
ImplementationExample:
select sum(quantity) assumOfQuantity from Productswhere category_id =1 and
subcategory_id =1;
select quantity,price from Productswhere category_id =1 and subcategory_id =1 order
by price desc;
select price from Productswhere category_id =1 and subcategory_id =1;
select max(price) from Productswhere category_id =1 and subcategory_id = 1;
UI Implementationand How toapply the same:

50 | P a g e

51 | P a g e

Amazon-Fresh-Project-Report (1)

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (19)

Similar to Amazon-Fresh-Project-Report (1)

Similar to Amazon-Fresh-Project-Report (1) (20)

Amazon-Fresh-Project-Report (1)