Amundsen is a metadata driven application for improving the productivity of data analysts, data scientists and engineers when interacting with data. It does that today by indexing data resources (tables, dashboards, streams, etc.) and powering a page-rank style search based on usage patterns (e.g. highly queried tables show up earlier than less queried tables). Think of it as Google search for data. The project is named after Norwegian explorer Roald Amundsen, the first person to discover the South Pole.
It includes three microservices and a data ingestion library.
- amundsenfrontendlibrary: Frontend service which is a Flask application with a React frontend.
- amundsensearchlibrary: Search service, which leverages Elasticsearch for search capabilities, is used to power frontend metadata searching.
- amundsenmetadatalibrary: Metadata service, which leverages Neo4j or Apache Atlas as the persistent layer, to provide various metadata.
- amundsendatabuilder: Data ingestion library for building metadata graph and search index. Users could either load the data with a python script with the library or with an Airflow DAG importing the library.
- amundsencommon: Amundsen Common library holds common codes among microservices in Amundsen.
- Python >= 3.4 (AmundsenDatabuilder: Python >= 2.7.x)
- Node = v8.x.x or v10.x.x (v11.x.x has compatibility issues)
- npm >= 6.x.x
Please note that the mock images only served as demonstration purpose.
-
Landing Page: The landing page for Amundsen including 1. search bars; 2. popular used tables;
-
Table Detail Page: Visualization of a Hive / Redshift table
-
Column detail: Visualization of columns of a Hive / Redshift table which includes an optional stats display
-
Data Preview Page: Visualization of table data preview which could integrate with Apache Superset
Want help or want to help? Use the button in our header to join our slack channel. Please join our mailing list as well.
Here is the list of organizations that are using Amundsen today. If your organization uses Amundsen, please file a PR and update this list.
Currently officially using Amundsen:
Please visit the Amundsen installation documentation for a quick start to bootstrap a default version of Amundsen with dummy data.
Please visit Architecture for Amundsen architecture overview.
Amundsen supports two kinds of "nodes" in its graph today:
- Tables (from Databases)
- People (from HR systems)
Amundsen can connect to any database that provides dbapi or sql_alchemy interface (which most DBs provide).
The databases we see most frequently used in the community are:
- Hive and anything that works with Hive metastore (Spark SQL, Presto, Athena, etc.)
- BigQuery
- PostgreSQL and anything that uses the same interface (Redshift)
- Snowflake
- Amazon Glue and anything built over it (like Databricks Delta - which is a work in progress).
Please visit Installation guideline on how to install Amundsen.
Please visit Roadmap if you are interested in Amundsen upcoming roadmap items.
- Amundsen - Lyft's data discovery & metadata engine (April 2019)
- Software Engineering Daily podcast on Amundsen (April 2019)
- How Lyft Drives Data Discovery (July 2019)
- Data Engineering podcast on Solving Data Discovery At Lyft (Aug 2019)
- Open Sourcing Amundsen: A Data Discovery And Metadata Platform (Oct 2019)
- Disrupting Data Discovery {slides, video} (Strata SF, March 2019)
- Amundsen: A Data Discovery Platform from Lyft {slides} (Data Council SF, April 2019)
- Disrupting Data Discovery {slides} (Strata London, May 2019)
- ING Data Analytics Platform (Amundsen is mentioned) {slides, video } (Kubecon Barcelona, May 2019)
- Disrupting Data Discovery {slides, video} (Making Big Data Easy SF, May 2019)
- Disrupting Data Discovery {slides, video} (Neo4j Graph Tour Santa Monica, September 2019)
- Disrupting Data Discovery {slides} (IDEAS SoCal AI & Data Science Conference, Oct 2019)
Join slack to find out about our next virtual community meetings. Notes: