A Scalable server architecture in social networking applications

PresenceCloud

Presenting By

BATTU DIVYA

INTRODUCTIONEXISTING SYSTEMPRPOSED SYSTEMMODULESSYSTEM CONFIGURATIONSSCREEN SHOTSCONCLUSION

AGENDA

Social networking services are growing . Many people communicating with the world using these.

A mobile presence service is an essential component of social networking applications.

If presence updates occur frequently, the enormous number of message distributed by presence servers may lead to scalability problem.

INTRODUCTION

To address this problem, we propose an efficient and scalable server architecture – Presence Cloud

Presence Cloud organizes presence servers into server-to-server architecture.

The performance can be analyzed in terms of search cost and search satisfaction level.

INTRODUCTION

3 popular commercial IM systems are : AIM, Microsoft MSN, Yahoo! Messenger.

They leverage some form of centralized clusters

Centralized clusters are used to provide presence services.

Storing the presence information is the one of the most messaging traffic in these instant messaging systems.

EXISTING SYSTEM

Peer – to- peer SIP has been proposed to remove centralized server.

And also P2PSIP reduces the maintenance costs and failures in server based deployment.

These clients are organized in DHT

Thus presence cloud can support large scale social network service among thousands of servers,

PROPOSED SYSTEM

Processor - Pentium – 3 Speed - 1.1 GHz RAM - 256 MB Hard Disk - 20 GB Floppy Drive - 1.44 MB Key Board - Standard Windows Key

Board Mouse - Two or Three button mouse Monitor - SVGA

HARDWARE CONFIGURATION

Operating System -windows95/98/2000/XP

Application Server - Tomcat 5.0/6.x Front End - HTML, Java, JSP Scripts - Java Script Server side scripts - Java server pages Database - MySQL Database Connectivity - JDBC

SOFTWARE CONFIGURATION

The modules we are discussing in this context are ::

Presence Cloud serve overlay

One – hop caching stratege

Directed Buddy Search

MODULES

PRESENCE CLOUD SERVER OVERLAY :• This construction algorithm organizes ps nodes in to

server – to – server overlay.• It provides a good low diameter property.• It ensure that a ps node needs only two hops.

ONE HOP CACHING STRATEGY :• To improve the efficiency, presence cloud requires a

caching strategy

MODULES

• In Presence Cloud, each PS node maintains a user list of presence information of the attached users.

• The cache is updated when neighbours establishes a connection to it. And it updated periodiaclly with it neighbours.

• Therefore, when any PS node recieves a query, it can respond not only with its own user list. But also matches in the user lists offered by all of its neighbours.

• Minimizing the searching response time is important in presence services

• By organizing the PS nodes into server-to-server overlay network, we can efficiently respond to the queries and can reduce the network traffic.

• By capitalizing one – hop caching, that it maintains user list of neighbors, we can improve response time by increasing the chances of finding buddies.

•Clearly, this mechanism reduces both network traffic and response time.

DIRECTED BUDDY SEARCH :

SCREEN 1

ADMIN LOGIN

PAGE

SCREEN 2

SELECTING

PRESENCE

SERVER

LOCATION

SCREEN 3

UPLOADING DATA

IN SERVER

SCREEN 4

USER

REGISTRATION

SCREEN 5

USER LOGIN PAGE

SCREEN 6

SEARCHING FOR

HOTELS IN USER

LOCATION

SCREEN 7

SEARCH RESULTS

FROM

PRESENCE

SERVERS

SCREEN 8

USERS’S DESIRED

RESULT WITH

LANDMARK

SCREEN 9

USER REVIEW

PAGE

CONCLUSION

Presence cloud Supports mobile presence services in large-scale social network services.

It achieves major performance gains in terms of the search cost and search satisfaction.

Facebook, http://www.facebook.com. Twitter, http://twitter.com. Foursquare http://www.foursquare.com. Google latitude,

http://www.google.com/intl/enus/latitude/intro.html. Buddycloud, http://buddycloud.com. Mobile instant messaging,

http://en.wikipedia.org/wiki/Mobileinstant messaging.

REFERENCES