You can now import the desired database schema from any ORM or other tool into Atlas,
and use it to automatically plan migrations for you.
See an example
Introduction
Today, I'm happy to share with you one of the most exciting features we've added to Atlas since its inception:
"External Schemas".
Atlas is a modern tool for managing your database schema. It allows you to inspect, plan, lint and execute schema changes
to your database. It is designed to be used by developers, DBAs and DevOps engineers alike.
Schema-as-Code
Atlas is built around the concept of database "Schema-as-Code", which means that you define the desired
schema of your database in a declarative way, and Atlas takes care of planning and executing the necessary
migrations to get your database to the desired state. The goal of this approach is to let organizations
build a single source of truth for complex data topologies, and to make it easy to collaborate on schema changes.
Schema Loaders
To achieve this goal, Atlas provides support for "Schema Loaders" which are different mechanisms for loading
the desired state of your database schema into Atlas. Until today, Atlas supported a few ways to load your schema:
- Using Atlas DDL - an HCL based configuration language for defining database schemas.
- Using Plain SQL - a simple way to define your schema using plain SQL files (CREATE TABLE statements, etc.)
- From an existing database - Atlas can connect to your database and load the schema from it.
- The Ent ORM - Atlas can load the schema of your Ent project.
Today, we are adding support for "External Schemas", which means that you can now import the desired database schema
from any ORM or other tool into Atlas, and use it to automatically plan migrations and execute them for you.