Hi everyone!
Welcome to the fifth edition of our newsletter, where we periodically share updates and fresh content about everything Atlas.
Here’s what you can find in this edition:
Read all about v0.10.0 and the Community Preview for Atlas Cloud in our most recent announcement blog post.
Fresh Atlas guides and videos covering topics from integration tests on GitHub Actions to preventing migration conflicts.
We’re starting to see Atlas pop up in community blog posts on various topics, so we included a few of those for you to read.
Happy weekend,
Ariel and Rotem
P.S. Have you joined our Discord server? Join us and the rest of the community for Atlas-related discussions and help
Atlas v0.10.0 annoucement
It's been two months since the release of v0.9.0, so we figured it's about time to release a new version and share with you what we've accomplished so far, as well as what's to come in the upcoming weeks. Besides the many improvements and bug fixes in v0.10.0, we added two major features to Atlas that I want to share with you: schema loaders and the Community Preview of Atlas Cloud.
Never break your production database again
Connect your migration directory to Atlas Cloud in less than 30 seconds, and get out-of-the-box continuous integration and time travel for your schema changes.
A free, community plan is available: get it here.
Integration tests for your database on GitHub Actions
When developing an application that uses a database, it's important to test your application against a real database. As good as your unit tests may be, some issues can only be caught by running proper integration tests.
Learn how in this guide.
From our YouTube channel
Detecting Migration Conflicts with Atlas
When two developers make conflicting changes to code on a project, Git will usually detect a conflict and prevent the conflicting code from being merged to the mainline branch.
Unfortunately, this doesn't work for developers planning schema migrations, since each will create a new file with a different name, and no conflict will be detected.
In this video, we discuss a simple but robust solution to detecting migration conflicts developed as part of Atlas, the open-source schema management tool that we maintain.
How to protect your database (from yourself)
Making changes to your database schema can be risky business. You can accidentally drop resources, break compatibility with your application, or cause it to lock in ways that cause downtime.
In this video, we show how you can use Atlas, an open-source schema management tool to prevent dangerous changes before they happen in production.
From the community
Build TypeSafe Node API using tRPC, Fastify, Kysely, and Atlas CLI
Build a full-stack application using Node.js, React and Atlas
Wrapping up
Thanks for reading this edition of the Atlas newsletter! If you have suggestions or requests for Atlas or this newsletter, feel free to drop us a line on Discord, Twitter, or GitHub