NOAA Product Distribution & Access - Where it is going and what can I expect?

As part of NOAA's Environmental Satellite Processing and Distribution System (ESPDS) Development program, Solers is building an enterprise system for NOAA that provides robust data ingest, processing, product generation, and distribution functions by employing enhanced computing methodologies and the latest technology improvements, including a Service Oriented Architecture (SOA). These enhancements, currently being developed, provide a secure, scalable, and adaptable infrastructure in response to changing demands.. The first major ESPDS Development effort is Product Distribution and Access (PDA), which leverages a SOA to modernize the ESPC distribution segment, and will be transitioned to the ESPC operational environment in 2014. In this presentation, Team Solers will provide an overview of the PDA architecture, design, and schedule. Some key features of PDA include: • SOA-based interfaces for integrating with data providers, as well as support for secure versions of FTP for non-SOA-enabled (legacy) data providers. • Use of push and pull approaches for consumers to obtain weather data, including HTTP(S) and secure versions of FTP. • Subscription-based distribution solution that allows consumers to submit subscription requests and either receive the data directly via secure push, or receive notification when the data is available. • The ability for consumers to search the 7-day PDA inventory, and submit one-time (ad-hoc) requests for data from the inventory. • The use of virtualization and dynamic resource management (leveraging VMware technology) to automatically manage the deployment of services and allocation of computing resources across a cluster of commodity x86 blade computing hardware. The major benefits that PDA provides over the current (legacy) ESPC distribution solution include: • New methods for integrating with data providers and consumers can be rapidly developed and deployed as independent services, thereby greatly reducing the time and complexity involved with integration. • The use of an Enterprise Service Bus (ESB) for inter-service communication enables loose coupling of services. It also allows different services to be deployed to different networks, in order to facilitate integration with a variety of data providers and consumers in a heterogeneous network environment via a single solution. • Multiple instances of each service are instantiated during run-time to provide scalability and high availability, and ensure that there is no single point of failure. Service instances can be dynamically increased and decreased at run-time as demand from data providers or consumers increases or decreases.