[Historical Document]

University California, Berkeley / NASA

End to End Problems & Solutions in EOSDIS

Contents:

This page:

• Introduction

This Site:

• Project overview page
• BigSurs main page.

Introduction

The UCB team is tasked with coordinating the implementation details between participating groups. Therefore, we have a hand in each aspect of the EOSDIS end to end problem mentioned in our parent page. Without going into every detail, we can summarize major efforts as follows. Keep in mind that the architecture is Database-Centric:

1. Development of:
• the Schema
• the Distributed Processing System (DPS)
• an "Application Programming Interface" (API)
• any and all management "tools" for the database environment
• "Eager" and "Lazy" processing engines
2. Data collection
3. Architecting an interface

1. More effective wide-area distributed-DBMS technology. Our efforts focus on a prototype distributed DBMS, called Mariposa.
2. A type library for optimally regridding satellite imagery (David Siegel).
3. An advanced visualization system for specifying user interactions with the database known as Tecate, headed by Peter Kochevar.
4. A more effective interface between a DBMS and a tertiary memory file system . This is a part of the High Performance Storage System Project, HPSS , headed by Dick Watson. Also see the National Storage Laboratory, NSL.
5. End-to-end modelling of the "end-to-end" problem of going from data source to DBMS to visualization system. The " Gator " project has as its goal to identify the ultimate bottlenecks in the overall architecture and then focus on parallelization of these modules. Gator is headed by Jim Demmel.
6. A more flexible wide-area networking protocol, headed by Joseph Pasquale.

Michael Stonebraker
621 Soda Hall
University of California
Berkeley, Ca. 94720

Partners and participants

Acknowledgements