Amundsen is a data discovery and metadata engine to enhance the productivity of data analysts, engineers, and data scientists while interacting with data. It is built on top of five different micro-services including front-end service, metadata service, Neo4j, Databuilder, and Search service and each of them needs to be deployed and sustained separately.

Features:
Data scientists have to spend a lot of time in the Data Discovery phase to try to understand what data exists, where it exists, who makes use of it, who owns it, and how to request access. In context to this, Amundsen helps the data team to be more productive by saving time spent in the discovery phase so that searching can be effectively done which ultimately saves time to do more findings.
Metadata Service: It manages metadata requests from the front-end service and other microservices as well. The persistent layer is Neo4j by default but it can easily be substituted.
Search Service: This service is backed by Elasticsearch to manage search requests from the front-end service. By default, the search engine is powered by ElasticSearch but this can be substituted as well.
Front-end Service: It hosts the web application of Amundsen.
Databuilder: It is a generic data ingestion framework that extracts metadata from multiple sources.
Common: It is a library repo that holds common codes among all microservices in Amundsen.

Why should you use Amundsen packed by ATH?
Up-to-date
Consistent between platforms
Secure