Earthdata Search Overview Earthdata Search (https://search.earthdata.nasa.gov) is a modern web application allowing users to search, discover, visualize, refine, and access NASA Earth Observation data using ESDIS’ wide array of service offerings. It's goal is to ease the technical burden on data users by providing a high-quality application that makes it simple to interact with NASA Earth observation data, freeing them to spend more effort on innovative endeavors. It also provides a way for EOSDIS to showcase its service offerings, including CMR and GIBS.  Image Removed Image Added
By nature of interfacing with the CMR, Earthdata Search has access to all of the EOSDIS earth science data along with the international holdings previously only available through the Global Change Management Directory system.
System Architecture  Image Removed Image Added Earthdata Search is a Ruby on Rails application with a heavy JavaScript front end. It relies on a small postgres instance in order to save various pieces of information such as user's projects. To understand how this tool is built, below are some key decisions that were made during design and implementation. Design Decisions with RationaleKnockout.js is used for the views and models. This allows a very simple observer-based system for managing change, speeding up development.Features with limited support (e.g. CWIC rendering) are placed in plugins separate from the main package. This keeps the overall footprint of the client manageable.Separate wrappers and adapters for the CMR API into small, well-defined areas and write tickets whenever we need to add to them. Eventually, use the CMR with limited transformation, directly from the browser, reducing overhead while improving accuracyserverless application built using React. It relies on AWS Lambda, API Gateway, and CloudFront along with a few other services to enable search, discovery, access and customization of EOSDIS data. Ranking of -ilitiesThe ranking of -ilities providers provides the developers of Earthdata Search a means by which to decide between different design options. As shown below, we value quality of the tool above all else, even though we ideally strive to ensure all -ilities are met at all times! Quality > Usability > Agility > Availability - Quality – We value simple, lightweight client design to ensure that we are able to maintain a high quality user experience via low bug rates. We work with service and metadata owners to improve the stack we are built on.
- Usability – Design is a fist-class citizen in our process and we constantly solicit feedback and metrics to ensure we are meeting user needs.
- Agility – We incorporate new capabilities and respond to user and data provider needs.
- Availability – We maintain a zero-downtime application.
Architecture Patterns UsedMVC – Model View Controller Separates concerns and allows varying uses of dataAsync Plugins – Reduces page size and improves performanceMVVM (via Knockoutjs) – Model View ViewModel allows for lightweight change observation
Key Trade-Offs- Graceful degradation over Universal support – We prefer to assume collections will have the best possible feature support and degrade gracefully if they do not, rather than coding to the lowest common denominator. This acts as a carrot for better service support and high-quality metadata.
- Simplicity over Feature richness – New features, especially in rich web applications, come at a cost of higher cognitive load on users decreased performance, and higher maintenance costs. We treat new features with appropriate weight and design solutions to minimize it
- Dumb client over Smart - We prefer the CMR, having more complete information, provide us with required metadata and a clean search API, rather than attempting to clean up gaps by adding translations, thereby decreasing the weight of the client and improving the API for other clients.
- Data over Opinions - We value collecting metrics and using A/B testing to validate the feedback we are getting to ensure that it is in the best interest of our large user audience and not just representative of the opinion of one user.
System Robustness and AvailabilityFault ToleranceSystem MonitoringThe Earthdata Search application provides a heart-beat monitoring mechanism to monitor the health status of the entire system. Upon detecting unresponsive services, for example due to loss of network connectivity or other problems, the system can automatically restart the applications, thereby improving fault tolerance of the system resulting in increased availability and robustness. System MonitoringAll Earthdata Search servers are monitored using Nagios, which is a system monitoring tool capable of monitoring the application and system health statuses and send alerts to the operator and/or system administrator via email notification upon detection of system anomalies or potential issues, allowing system issues to be taken care of in a timely manner. Hardware Redundancyuses built AWS monitoring services to ensure the system is highly available. If an issue resulting in the loss of service is encountered, our team is alerted and the issue is prioritized for resolution immediately. Horizontal ScalingEarthdata Search is architected to scale horizontally to ensure a highly performant application regardless of the load placed on the app.The Earthdata Search is architected using redundant application server platforms to balance the data storage and processing. The application has full redundancy in its operational environment from the storage layers up to the application layers. | 