Why it is hard to build a long-running service on PlanetLab

Authors:
Justin Cappos;John Hartman
Affiliations:
Computer Science Department, University of Arizona, Tucson, AZ;Computer Science Department, University of Arizona, Tucson, AZ
Venue:
WORLDS'05 Proceedings of the 2nd conference on Real, Large Distributed Systems - Volume 2
Year:
2005

Citing 4
Cited 3

A blueprint for introducing disruptive technology into the Internet

ACM SIGCOMM Computer Communication Review
Proper: privileged operations in a virtualised system environment

ATEC '05 Proceedings of the annual conference on USENIX Annual Technical Conference
Reliability and security in the CoDeeN content distribution network

ATEC '04 Proceedings of the annual conference on USENIX Annual Technical Conference
Democratizing content publication with coral

NSDI'04 Proceedings of the 1st conference on Symposium on Networked Systems Design and Implementation - Volume 1

Learning from PlanetLab

WORLDS'06 Proceedings of the 3rd conference on USENIX Workshop on Real, Large Distributed Systems - Volume 3
Implementing and operating an internet scale distributed application using service oriented architecture principles and cloud computing infrastructure

Proceedings of the 10th International Conference on Information Integration and Web-based Applications & Services
Seattle: a platform for educational cloud computing

Proceedings of the 40th ACM technical symposium on Computer science education

Quantified Score

Hi-index	0.00

Visualization

Abstract

PlanetLab was conceived as both an experimental testbed and a platform for long-running services. It has been quite successful at the former, less so at the latter. In this paper we examine why. The crux of the problem is that there are few incentives for researchers to develop long-running services. Research prototypes fulfill publishing requirements, whereas long-running services do not. Several groups have tried to deploy research services, long-running services that are useful, but also novel enough to be published. These services have been generally unsuccessful. In this paper we discuss the difficulties in developing a research service, our experiences in developing a research service called Stork, and offer suggestions on how to increase the incentives for researchers to develop research services.