Top all-time · #4304
Atlas Blog
Company blog · atlasgo.io/blog · on HN as a8mdataprogramming
Atlas Blog is the company blog at atlasgo.io, writing about data and programming. Since 2022, 18 different Hacker News readers have linked it 28 times, most often “Atlas – Terraform but for Database Migrations”. It is still writing: the last post was on 2026-10-08, and you can follow it by feed.
Too few sampled comments (12) to say how often HN recommends it.?
Why HN links it
HN commenters point to atlasgo.io as a database schema migration tool, mostly for declarative schema management and linting. The comments treat it as a tool rather than praising its writing.
Summarised by Claude from a sample of 12 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Database schema as code for engineers and AI agents. Atlas plans, lints, tests, and deploys migrations for PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, ClickHouse, Snowflake, Databricks, Lakebase, Redshift, Spanner, CockroachDB, and more.
Most-linked posts?
- Atlas – Terraform but for Database Migrations7 people · 8 mentions · first linked 2022-01-21
- The Myth of Down Migrations2 people · 3 mentions · first linked 2024-04-01
- /2 people · 2 mentions · first linked 2022-01-23
- /guides/orms/sqlalchemy2 people · 2 mentions · first linked 2024-08-29
What Hacker News says?
I'm pretty sure they mean https://atlasgo.io/ and not https://atlas.apache.org/ .
Comment linking /
on “Liquibase continues to advertise itself as "open source" despite license switch”Submitted Atlas – Terraform but for Database Migrations as a story · 237 points
HN discussionhttps://atlasgo.io/ or https://github.com/djrobstep/migra
Comment linking /
on “PostgreSQL Schema Change Guide”Submitted Terraform for databases: Announcing the official Terraform provider for Atlas as a story · 12 points
HN discussionHi manigandham! One of Atlas's creators here. Thanks for the feedback! I completely understand your point here, and I would add that for many use cases the declarative approach isn't robust enough for schema migrations. The classic example being, how does a tool discern between a column drop/add and a rename, and how does the migration tool allow for backward-compatible schema evolution? For this reason, as you can…
Comment linking /
on “Atlas – Terraform but for Database Migrations”Submitted Go Tests "Go Test" as a story · 6 points
HN discussionSchema management tools often include built-in linters. I added a linter engine to my MySQL/MariaDB schema management tool Skeema back in 2019 and it proved to be a popular feature [1]. A couple more recent entrants in this space include ByteBase [2] and Atlas [3]. When selecting a linter, I'd just recommend ensuring the author(s) are deeply experienced in your particular DBMS. Otherwise they tend to cargo-cult bad…
Comment linking /versioned/lint
on “Database Linting and Analysis for PostgreSQL”Submitted The Myth of Down Migrations as a story · 6 points
HN discussionFrom their docs [1] it seems that they support a workflow similar to Terraform. [1]: https://atlasgo.io/declarative/apply
Comment linking /declarative/apply
on “A Language Server for Postgres”Submitted Why Your Team Needs a Database Schema-as-Code Tool as a story · 6 points
HN discussionSomething like https://atlasgo.io/ ?
Comment linking /
on “A Language Server for Postgres”Submitted The Myth of Down Migrations as a story · 5 points
HN discussionIn terms of automating migrations in postgres, I really want declarative migrations and only the safe subset too. The overhead of having a schema defined over a bunch of migrations seems non ideal. The closest tool I've found here is: https://atlasgo.io/
Comment linking /
on “When Postgres blocks: tips for dealing with locks”Submitted Atlas Migration Execution Engine – Atlasgo.io as a story · 3 points
HN discussionWhat they need is a proper migration diff and generation tool with strong defaults. Alembic is meh and the DX is poor. Prisma and Django's migration/diff tools are the gold standard. (There's also Atlas for Python but it isn't much better, a lot of fiddly config files https://atlasgo.io/guides/orms/sqlalchemy )
Comment linking /guides/orms/sqlalchemy
on “What's New in SQLAlchemy 2.1?”Submitted Prevent destructive changes to your database with the Atlas GitHub Action as a story · 3 points
HN discussionI'm glad to see I'm not the ~only one bothered by this issue. This has been, and still is, one of the challenges in managing MySQL schemas. That's one of the reasons we implemented "migrate down" differently than other tools. I'm not here to promote my blog post, but if you are interested in seeing how we tackled this in Atlas, you can read more here: https://atlasgo.io/blog/2024/04/01/migrate-down
Comment linking /blog/2024/04/01/migrate-down
on “Building a better and scalable system for data migrations”Submitted 5 Strategies for Reliable Schema Migrations as a story · 2 points
HN discussionI have been eyeing up https://atlasgo.io/ - I am going to give it a whirl soon.
Comment linking /
on “Building a better and scalable system for data migrations”Submitted Atlas v1.1: Database Security as Code and Declarative Data Management as a story · 1 points
HN discussionGood point regarding ORMs - that was one of the main problems I wanted to tackle when we built Atlas ( https://atlasgo.io ). We added support for reading ORM definitions directly, then let you extend the "base schema" defined in them. For example, you can define your models in SQLAlchemy, EF Core, Ent, or others as a partial schema, and then extend it with functions, views, and additional objects. From there, Atlas…
Comment linking /guides/orms/sqlalchemy
on “CLI to manage your SQL database schemas and migrations”Submitted Atlas, the “Terraform for databases” can now plan migrations for you as a story · 1 points
HN discussionfwiw, I personally am interested in this approach too[0]. I keep running into roadblocks around the ordering of events and some of the hairy issues around "destructive" actions (eg: renaming columns). i think we can get there, especially once we make progress with this LSP. There are other notable mentions in this space: Reshape: https://fabianlindfors.se/blog/schema-migrations-in-postgres... Atlas: https://atlasgo.…
Comment linking /
on “Show HN: Postgres Language Server”Have a look at https://prisma.io or https://atlasgo.io
Comment linking /
on “Ask HN: How can I get clean solution for migrations in Node.js?”Ariel from Atlas here. This setup is pretty common (declarative locally, versioned in real environments). Since migrations are auto-generated (by Atlas) on PRs, most developers never touch the versioned workflow directly. See: https://atlasgo.io/concepts/declarative-vs-versioned#combini... , and https://github.com/ariga/atlas-action?tab=readme-ov-file#ari...
Comment linking /concepts/declarative-vs-versioned
on “Sqldef: Idempotent schema management tool for MySQL, PostgreSQL, SQLite”Intermixing tools and processes like that will create a bunch of pain. Even Atlas seems to realize this (probably from customer feedback) as they offer the "versioned" mode that looks exactly like what we do today. https://atlasgo.io/versioned/intro Note how this section of the docs is much longer than the declarative version. One of the hard parts about adopting something like this is that it's easy for new project…
Comment linking /versioned/intro
on “Declarative database schema migrations – yay or nay?”thanks for contributing this! i will definitely check it, was thinking about using https://atlasgo.io/ for declarative sql code, glad there is another option!
Comment linking /
on “Show HN: SRTD – Live-reloading SQL templates for Supabase migrations”
