1. OPeNDAP in the Cloud OPeNDAP James Gallagher, Nathan Potter and NOAA/NODC Deirdre Byrne, Jefferson Ogata, John Relph 26 June 2013

2. Not only is the OPeNDAP request smaller, it's also just the data the person wants Full dataset OPeNDAP request 4% Download100% Download

3. Not only is the OPeNDAP request smaller, it's also just the data the person wants Full dataset OPeNDAP request 4% Download100% Download

4. NOAA Environmental Data Management Conceptual Cloud Architecture* Potential locations of cloud-enabled OPeNDAP instances *Aadapted from NOAA Environmental Data Management Framework Draft v0.3 Appendix C - Dr. Jeff de La Beaujardière, NOAA Data Management Architect

5. No vendor lock-in! No Stovepipes! - flexible storage method (what is the client of 2020? we don't know!) Hierarchical/human browsable Constraints file dataset file

6. No vendor lock-in! No Stovepipes! - flexible storage method (what is the client of 2020? we don't know!) Hierarchical/human browsable Constraints file dataset file

7. Solution: Data Store Catalog Data S3 HTTP GET & HEAD requests

8. Solution: Data Store Catalog Data S3 HTTP GET & HEAD requests

9. Solution: Data Store Catalog Data S3 HTTP GET & HEAD requests

10. Solution: Data Store Catalog Data S3 HTTP GET & HEAD requests

11. Web requests S3 Catalog, or data request XML or data file

12. To enhance performance, data were accessed from S3 only when not already cached. OPeNDAP Catalog requests S3 OPeNDAP Server catalog cache XML File User catalog Request Catalog Access THREDDS catalog or HTML EC2 data cache

13. To enhance performance, data were accessed from S3 only when not already cached. OPeNDAP Data requests S3 OPeNDAP Server catalog cache Data File User data Request Data Access Data Slice EC2 data cache

14. To enhance performance, data were accessed from S3 only when not already cached. OPeNDAP Data requests S3 OPeNDAP Server catalog cache Data File User data Request Data Access Data Slice EC2 data cache

15. Observations S3FS & Amazon's APIs: vendor lock-in

16. Observations S3FS & Amazon's APIs: vendor lock-in XML catalogs were flexible

17. Observations S3FS & Amazon's APIs: vendor lock-in XML catalogs were flexible Catalogs didn't need to be stored in S3

18. Observations S3FS & Amazon's APIs: vendor lock-in XML catalogs were flexible Catalogs didn't need to be stored in S3 Glacier: Places additional demands on clients.

19. Summary OPeNDAP server with minimal changes Served data stored in S3

20. Summary OPeNDAP server with minimal changes Served data stored in S3 Data accessible to other systems Solution widely applicable