70 likes | 219 Views
Evolving Architecture at NSIDC. M. J. Brodzik. Evolving Architecture at NSIDC. To. From. Stovepipe applications Minimal layered architecture Difficult (impossible) to scale systems up, extend systems for related purposes, or reuse good ideas elsewhere. Enabling “Community-driven” APIs
E N D
Evolving Architectureat NSIDC M. J. Brodzik ESDIS visit to NSIDC , 4/2011
Evolving Architecture at NSIDC To From Stovepipe applications Minimal layered architecture Difficult (impossible) to scale systems up, extend systems for related purposes, or reuse good ideas elsewhere Enabling “Community-driven” APIs Internal collaborations to build infrastructure (more flexible, scalable, maintainable, robust) Multiple projects with similar needs work together for common solution NSIDC leading the way: “more data to more users” Engaging useful IT trends (developing collaborative services across archives and data centers) Modular design allows good ideas from a given project to be more easily reused
Evolving Architecture at NSIDC: Past • Stovepipe applications • No common processing environment • Minimal use of external services or components • Minimal data-driven processes
Evolving Architecture at NSIDC: Current Production@NSIDC • Common web application environment • OpenSearch services: community-standard web services for discovery and access • Advanced plot & analysis web apps developed (but not available as web services) • Developing some external components & services • Metrics capabilities moving to services, rather than GUI responsibility
Evolving Architecture at NSIDC: Future Production@NSIDC • “OS+” = NSIDC-proposed extensions to ESIP Federated Search • Polaris replaces Advanced Search • MDDB obsolete • EDB + Searchlight infrastructure enables file- and collection-level services
Evolving Architecture at NSIDC Shared infrastructure plan enables Scalability (that was impossible with stovepipes) Robust core that is reused for multiple projects, so project can focus on the project’s specialty goals Selective reusability (stovepipes tended to “all or nothing” on maintenance/reuse decisions) allows one project’s good ideas to continue after the life of the project Maintainability (critical mass of teams working solutions, not just one “expert”) Accountability of developers to one another, to build higher-quality software Use of standards (format, metadata interchange, web service protocols) leverages work of large external communities to bring “more data to more users” in meaningful contexts
Evolving Architecture at NSIDC • Questions? Discussion