{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2026,5,11]],"date-time":"2026-05-11T11:30:37Z","timestamp":1778499037090,"version":"3.51.4"},"reference-count":4,"publisher":"Association for Computing Machinery (ACM)","issue":"1","license":[{"start":{"date-parts":[[2006,1,1]],"date-time":"2006-01-01T00:00:00Z","timestamp":1136073600000},"content-version":"vor","delay-in-days":0,"URL":"https:\/\/www.acm.org\/publications\/policies\/copyright_policy#Background"}],"content-domain":{"domain":["dl.acm.org"],"crossmark-restriction":true},"short-container-title":["SIGOPS Oper. Syst. Rev."],"published-print":{"date-parts":[[2006,1]]},"abstract":"<jats:p>\n            PlanetLab is a geographically distributed platform for deploying, evaluating, and accessing planetary-scale network services. PlanetLab is a shared community effort by a large international group of researchers, each of whom gets access to one or more isolated\n            <jats:italic>slices<\/jats:italic>\n            of PlanetLab's global resources. Because we deployed PlanetLab and started supporting users before we fully understood what its architecture would be, being able to evolve the system became a requirement. This paper examines the set of\n            <jats:italic>design principles<\/jats:italic>\n            that guided this evolution. Some of these principles were explicit at the project outset, and others have become crystallized as the platform has developed.\n          <\/jats:p>","DOI":"10.1145\/1113361.1113367","type":"journal-article","created":{"date-parts":[[2006,2,6]],"date-time":"2006-02-06T18:14:10Z","timestamp":1139249650000},"page":"11-16","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":69,"title":["The design principles of PlanetLab"],"prefix":"10.1145","volume":"40","author":[{"given":"Larry","family":"Peterson","sequence":"first","affiliation":[{"name":"Princeton University"}],"role":[{"role":"author","vocabulary":"crossref"}]},{"given":"Timothy","family":"Roscoe","sequence":"additional","affiliation":[{"name":"Intel Research - Berkeley"}],"role":[{"role":"author","vocabulary":"crossref"}]}],"member":"320","published-online":{"date-parts":[[2006,1]]},"reference":[{"key":"e_1_2_1_1_1","volume-title":"Proc. 1st NSDI","author":"Bavier A.","year":"2004"},{"key":"e_1_2_1_2_1","doi-asserted-by":"publisher","DOI":"10.1145\/52324.52336"},{"key":"e_1_2_1_3_1","doi-asserted-by":"publisher","DOI":"10.1145\/1113361.1113376"},{"key":"e_1_2_1_4_1","volume-title":"Proc. of ACM HotNets-I","author":"Peterson L.","year":"2002"}],"container-title":["ACM SIGOPS Operating Systems Review"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1113361.1113367","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/1113361.1113367","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T16:18:47Z","timestamp":1750263527000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1113361.1113367"}},"subtitle":[],"short-title":[],"issued":{"date-parts":[[2006,1]]},"references-count":4,"journal-issue":{"issue":"1","published-print":{"date-parts":[[2006,1]]}},"alternative-id":["10.1145\/1113361.1113367"],"URL":"https:\/\/doi.org\/10.1145\/1113361.1113367","relation":{},"ISSN":["0163-5980"],"issn-type":[{"value":"0163-5980","type":"print"}],"subject":[],"published":{"date-parts":[[2006,1]]},"assertion":[{"value":"2006-01-01","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}