netflix/atlas

In-memory dimensional time series database.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Added to GitGenius on September 19th, 2026
Created on August 5th, 2014
Open Issues & Pull Requests: 8 (+0)
GitHub issues: Enabled
Number of forks: 358
Total Stargazers: 3,565 (+0)
Total Subscribers: 508 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 68.3 days
Mean response time: 851.7 days
90th percentile: 2815.0 days
Tracked items: 14

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 7
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 2,563 days
Stale 30+ days: 7
Stale 90+ days: 7

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (12)
  • usability (6)
  • discussion (4)
  • help wanted (2)
  • bug (1)
  • question (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Atlas is an in-memory dimensional time series database backend for managing time series data.

The tool addresses the need to store and query high-cardinality dimensional metrics efficiently. It holds time series data in memory and organizes it by dimensions, allowing queries that filter and aggregate across multiple tagged attributes. This approach enables fast retrieval of metrics grouped by arbitrary combinations of tags, which is essential for monitoring systems that need to slice data across many dimensions like service, region, instance, or endpoint.

Atlas suits organizations running large-scale monitoring infrastructure where dimensional queries against high-cardinality data are frequent. It works well for teams already invested in Netflix's ecosystem or those building custom monitoring backends that require fine-grained control over time series storage and querying. The in-memory design makes it best suited for environments where the working set of metrics fits within available RAM and where query latency is a priority over long-term historical storage.

The project maintains steady development activity with regular issue engagement and ongoing maintenance. Pull requests receive consistent review and integration. The codebase shows active refinement of core functionality rather than major architectural shifts. Documentation is actively maintained alongside code changes. The project sustains a mailing list for community discussion and support.