www.xdegrees.com

Network Applications:What? Why? How?

Presented by Michael TanneCEO, XDegrees, Inc.

mtanne@xdegrees.com

O'Reilly Peer-to-Peer Conference2/15/2001

What is a Network Application?What is a Network Application?

3

What?Internet is evolvingInternet is evolving

The Internet is evolving into a network that is always on, multi-directional, and executable

Servers

PCs PCs

4

Network Applications will utilize Client-server and peer-to-peer interaction as needed

What?P2P and Client/Server will Co-existP2P and Client/Server will Co-exist

Client/Server Peer to Peer

Peer-to-peer applications and web applications are currently isolated from each other

Server to Server

Peer to Peer

Client/Server

“P2P technology has potential to reshape corporate computing architecture but it will start with augmenting existing infrastructures.”

5

What?Use clients AND serversUse clients AND servers

Some tasks make more sense on a client; some make more sense on a server

Server: Search, databases, financial transactions

Client: file transfer, publishing/sharing, storage

6

What?New class of applicationsNew class of applications

Putting this together, Network Applications are a new class of applications that execute on and leverage the resources of all parts of the network…

ClientsServers

Files

Services

MachinesDevices

Users

                

Why?Why?

Benefits to making your application a Network Application

8

Why?Decreased frictionDecreased friction

• Make publishing easier

– Avoid uploading, layout, provisioning, maintenance

• Increase application usage

– Users share more resources if they dont have to upload them to a remote server

• Ad-hoc collaboration with minimal IT support, but still IT oversight

• Result: greater productivity – better information

X-OutlookShare documents peer-to-peer from within an application people already use.

No need to email documents back and forth.

Photo SharingShare photos directly between user machines.

No need to take the time to upload photos to share them.

9

Why?Control of own resourcesControl of own resources

• User creates, manages and shares data in natural environment (his PC)

• Give administrators a "server-like" view on distributed resources

• Result: blend best of centralized and decentralized control

(yet central administration)(yet central administration)

X-OutlookThe user interacts with files on the server as if they were on his own desktop or laptop PC.

When he takes his laptop on a trip, all of his contacts and appointments are on his laptop.

ApplicationsOn a PC

10

Why?Aggregate and buffer unreliable resourcesAggregate and buffer unreliable resources

• Treat servers and PCs as one reliable resource

• Access information whether source is available or not

• Result: reliable network out of unreliable components

Enterprise StorageStore enterprise data redundantly on end-user machines.

Leverage network resources more effectively.

=

11

Why?Improve cost-structure and scalabilityImprove cost-structure and scalability

• Store applications and data on end-user machines

• Queue resources on servers as needed to maintain user experience

• Result: reduced server costs

Photo SharingPhoto sharing services reduce storage costs and maintain quality of service.

$$$ $

12

Why?Improved performance, less bandwidthImproved performance, less bandwidth

• Distributed systems handle traffic peaks more effectively

• Download from server, propagate via clients

• Result: improved peak performance

Anti-Virus

Distribute enterprise virus definition files (.DAT files) peer-to-peer.

Improve speed of virus update propagation when new viruses attack.

13

Why?Use web applications everywhereUse web applications everywhere

• Web applications are currently only useful when users are online

• Network Application seamlessly…– Stores data and executes application

locally when offline– Leverages central database and new

services when online

Sales Force Automation ASPAllow sales force to access SFA application locally if not connected to the corporate network.

DisconnectedConnected

How?How?

Seven things you need to make your application a Network Application

15

How?IP is like Parking South of MarketIP is like Parking South of Market

• A recent SOMA Parking Study(SPUR, Jul 19, 2000) Shows:

• Parking Spaces: 23,830 Parking Demand: 27,250

• Shortfall: 3420

• Servers are the tenants with fixed IP addresses

• Clients are visitors, who drive around until someone pulls out

• Tens of millions of new devices need IP addresses

16

How? Resource addressabilityResource addressability

• Need to be able to easily address resources– files, applications, people, machines and devices

• Consistent namespace mechanism across applications

• Logical abstraction between names and physical location

• Handle intermittent nature of clients

• Like DNS, but handle dynamic IP and other resources

• Allow for selection of "best" source of a resource

11

net.acme.com/sales/pricelist.pdf

206.55.128.15

155.12.37.135

55.12.37.135

X

201.235.15.12

17

Clinton

GWB

How? Resource availabilityResource availability

Directory Service

12 4

Unreliable resources

Reliable network

22

3

6

Greenspan

5

Clinton, G

reenspan

18

How? SecuritySecurity

• Distributed systems are more complicated to secure– No central point of control

• User authentication– Ensure that users are whom they claim to be

• Permissions– Control access to resources

• Encryption– Prevent unauthorized access to resources– DES 128 or AES

• Content validation– Digital Signature - MD5 or SHA-1– Ensure resources cannot be manipulated and presented as original

33

19

How? Web CompatibilityWeb Compatibility

• Need to be sure Network Application supports web-centric world

• Resources should be accessible using a browser

• Namespace should be compatible with DNS

• Web-based applications (CGI, ASP, Java, Javascript) should be accessed easily

44

20

How? ReliabilityReliability

• Integrating with mission critical applications

• As important as system features– Reliability – minimal downtime for application– Scalability – cost and effort to accommodate usage growth– Performance – experience and latency for end-users

• Look for solution that can grow with application

55

21

How? Application DesignApplication Design

• Determine optimal application architecture

• What goes on the server?– Database, directory, high bandwidth, cache, etc.

• What goes on the clients/peers?– User data, distributed traffic, remote/untethered operation

• Partition code to run at respective places

• Create client-side code to manage peer functions

66

Cache

ServerApplication

ClientApplication

Directory ServerDBMS

22

How? Easy integrationEasy integration

• Decide on user interface– Web browser, standalone application or integrated into

existing application

• Minimal change required by end-user– Don’t make user learn a new application

• Seek simple integration with existing application

• Support for standard protocols and development models– SOAP/XML, Java, http, URLs

• Consider Microsoft .NET and Sun ONE, UDDI, other Web services approaches

77

23

How?Natural LayersNatural Layers

• Not everyone builds the entire "stack"

• Make vs. buy decision for each layer

O/S

Addressability, Caching, Security

Search, DRM, Billing, Payments

WorkgroupCRM, etc.

Photo Sharing

Network Applications Stack

Applications

Services

Infrastructure

SystemO/S

Web Server, Application Server

Search, CND, Caching, ad serving

Portals ASP

Web Applications Stack

24

What? Why? How?Network ApplicationsNetwork Applications

• What?– New class of applications– Leverage all of the resources of the network – Improve applications and their delivery

• Why?– Better leverage of existing resources– Improved experience for user– More efficient cost structure

• How?– Examine 7 key issues– Make versus buy decisions

25

To turn your application into a Network Application, visit