Understanding Database Transactions in Rails

Few things are scarier than a database slowly losing integrity over weeks or years. For a while, nobody notices anything. Then users start reporting bugs, yet you can't find any code that's broken. By the time you realize the problem, it may be happening for so long that your backups are unusable. We can avoid problems like these with skillful use of transactions. In this article, Kingsley Silas introduces us to transactions at the database level, discusses when they should be considered, and shows us how to use them in Rails.

When you're in charge of a Rails app, there are a couple of areas where you really don't want to have problems:

  • Data Integrity - Does the data in your database make sense?
  • Database Performance - Do your queries return in a reasonable amount of time?

Database transactions (and their ActiveRecord counterparts) are powerful tools for avoiding these problems. Properly used, they can speed queries and ensure data integrity.

This article will introduce you to the concept of database transactions. It will also show you how to use them in Rails; but just as importantly, it will help you decide when to use them.

One cool thing about transactions is that they're actually implemented by the database. You can use them anywhere you use Postgres/MySQL/etc. Even if you're not a Ruby/Rails developer, the techniques you learn here will come in handy.

What Is A Transaction?

Transactions are typically used when you need to ensure data integrity, even if your web app crashes in the middle of a request.

From the Rails API docs

Transactions are protective blocks where SQL statements are only permanent if they can all succeed as one atomic action. The classic example is a transfer between two accounts where you can only have a deposit if the withdrawal succeeded and vice versa. Transactions enforce the integrity of the database and guard the data against program errors or database break-downs. Basically, you should use transaction blocks whenever you have a number of statements that must be executed together, or not at all.

A Classic Example

To illustrate why transactions are useful, let's consider a possible scenario.

Imagine that we are building a banking system that lets people transfer money. When John Doe (in Chicago) sends \$200 to Jane Doe (in London), we perform several DB operations.

  1. Check that John Doe has \$200 in his account.
  2. Debit the total amount from his account.
  3. Convert \$200 to Jane Doe's preferred currency, which is pounds.
  4. Credit Jane Doe's account.

funds transfer

An expensive problem

Implemented naively, our code might look like this:

sender.debit_account(amount) if sender.sufficient_balance(amount)
credit_amount = convert_currency(amount, recipient)
perform_transfer(recipient, credit_amount, sender)

What happens if our program crashes during the currency conversion? It's a crucial spot:

  • After money has been taken out of John's account
  • ...and before it's added to Jane's?

The money vanishes into thin air.

We need some way to ensure that errors along the way cause the database to roll back to avoid committing incomplete data. Either all of the database actions are performed, or none of them are.

Wrapping the above queries in a database transaction is your best bet for achieving data integrity.

In Rails, it might look like this:

Transfer.transaction do
  sender.debit_account(amount) if sender.sufficient_balance(amount)
  credit_amount = convert_currency(amount, recipient)
  perform_transfer(recipient, credit_amount, sender)

Now, even though we might be creating and updating records, the supposed changes are not reflected in the database until the transaction is completed successfully.

States of Database Transaction

Transactions have a well-defined life cycle. At any point in time, your transaction will be in a specific state.

Database Transaction States Source: https://www.tutorialspoint.com

  • Active: Our DB operations are being executed.
  • Partially Committed: Our DB operations have completed successfully, but changes have not been committed to the database, and cannot be accessed outside of the transaction.
  • Committed: Our DB operations have completed successfully and saved any changes to the DB.
  • Failed: Some error has occurred, which caused the DB to stop the transaction. The DB has not been rolled back at this point.
  • Aborted: The DB has been rolled back after a failure, and the transaction is done.

Transactions in ActiveRecord

We previously saw that our bank transfer code looked like this:

ActiveRecord::Base.transaction do
  sender.debit_account(amount) if sender.sufficient_balance(amount)
  credit_amount = convert_currency(amount, recipient)
  perform_transfer(recipient, credit_amount, sender)

We're calling the transaction method on the ActiveRecord::Base class and passing it a block. Every database operation that happens inside that block will be sent to the database as a transaction.

If any kind of unhandled error happens inside the block, the transaction will be aborted, and no changes will be made to the DB.


In the above example, I am calling the transaction method on the ActiveRecord::Base class. You might find yourself doing this in controller or service code.

Every ActiveRecord model has a transaction method. Imagine that you have a Transfer class that inherits from ActiveRecord. The following works:

Transfer.transaction do


Every instance of your ActiveRecord models, also has its own transaction method.

transfer = Transfer.new(...)
transfer.transaction do

And, because the transaction method is an ordinary Ruby method, we can reference it in our model definitions:

class Transfer < ApplicationRecord
  def perform(...)
    self.transaction do

How to Abort Transactions

To manually abort a transaction and prevent any of its changes from being written to the DB, you can use the ActiveRecord::Rollback method.

ActiveRecord::Base.transaction do
  @new_user = User.create!(user_params)
  @referrer = User.find(params[:referrer_id])
  raise ActiveRecord::Rollback if @referrer.nil?

Exceptions During Transactions

Any unhandled exception that occurs during the transaction will also cause it to be aborted. There are two common ways to raise these exceptions:

  • Using ActiveRecord methods ending with an exclamation-mark: save!, update!, destroy! etc.
  • Manually raising an exception

In ActiveRecord, when a method name ends with an exclamation-mark (also called a "bang"), it will raise an exception on failure.

Let's say we have a transaction that involves creating a new user account, while also updating the record of another user (the referrer):

ActiveRecord::Base.transaction do
  @new_user = User.create!(user_params)

The create! and update! methods will raise an exception if something goes wrong.

If we were to use the create and update methods (without the exclamation mark), they would indicate a failure via their return value, and the transaction would keep running.

Of course, we could always check the return value ourselves and "manually" raise an exception if we wanted to:

ActiveRecord::Base.transaction do
  @new_user = User.create(user_params)
  raise ActiveRecord::RecordInvalid unless @new_user.persisted?

It doesn't matter what kind of exception you raise. Any exception class will abort the transaction.

Don't forget to rescue the exception if you need to.

def create_referrer_account
  ActiveRecord::Base.transaction do
    raise ActiveRecord::RecordInvalid if @referrer.nil?
  rescue ActiveRecord::RecordInvalid => exception # handle error here...

Nested Transactions

The transactions we've seen so far only allow you to work with a single database. Most Rails apps only use one database, so that works out nicely.

If you need to ensure data integrity across multiple databases, you can do so by nesting ActiveRecord transactions.

In the example below, imagine that the User and Referrer models point to different databases.

User.transaction do
  @new_user = User.create!(user_params)
  Referrer.transaction do

If any parts of the inner transaction fail, it will cause the outer transaction to be aborted.

Beware, though, that nested transactions can be tricky to get right. It's best to avoid them if you can.

Transaction Tradeoffs

In programming, as in life, very few things are free. Transactions give us an excellent way to ensure data integrity, but they have a few possible drawbacks:

  • Performance - Using a transaction will consume more resources on the DB server than the raw queries.
  • Complexity - When overused, transactions can make your code more brittle and harder to understand.

For example, when you use a transaction in Rails, it ties up one of your DB connections until all the code in your transaction block finishes running. If the block contains something slow, like an API call, you could tie up a DB connection for an unreasonable amount of time.

ActiveRecord::Base.transaction do

The key to using transactions well is to use them only when you really need them.


With great power comes great responsibility.

Transactions give developers the power to write SQL statements in the right way. This power has a great responsibility attached to it - one that should not be abused by sprinkling transactions everywhere.

In addition to what we have learned, here is a checklist I came with for when I use transactions:

  1. Do I need to handle more than one SQL statement?
  2. Do I need the SQL statement to succeed together?

While you make use of transactions, ensure you're raising and rescuing the errors as we saw above.

What to do next:
  1. Try Honeybadger for FREE
    Honeybadger helps you find and fix errors before your users can even report them. Get set up in minutes and check monitoring off your to-do list.
    Start free trial
    Easy 5-minute setup — No credit card required
  2. Get the Honeybadger newsletter
    Each month we share news, best practices, and stories from the DevOps & monitoring community—exclusively for developers like you.
    author photo

    Kingsley Silas

    Kingsley works as a software engineer and enjoys writing technical articles.

    More articles by Kingsley Silas
    Stop wasting time manually checking logs for errors!

    Try the only application health monitoring tool that allows you to track application errors, uptime, and cron jobs in one simple platform.

    • Know when critical errors occur, and which customers are affected.
    • Respond instantly when your systems go down.
    • Improve the health of your systems over time.
    • Fix problems before your customers can report them!

    As developers ourselves, we hated wasting time tracking down errors—so we built the system we always wanted.

    Honeybadger tracks everything you need and nothing you don't, creating one simple solution to keep your application running and error free so you can do what you do best—release new code. Try it free and see for yourself.

    Start free trial
    Simple 5-minute setup — No credit card required

    Learn more

    "We've looked at a lot of error management systems. Honeybadger is head and shoulders above the rest and somehow gets better with every new release."
    — Michael Smith, Cofounder & CTO of YvesBlue

    Honeybadger is trusted by top companies like:

    “Everyone is in love with Honeybadger ... the UI is spot on.”
    Molly Struve, Sr. Site Reliability Engineer, Netflix
    Start free trial
    Are you using Sentry, Rollbar, Bugsnag, or Airbrake for your monitoring? Honeybadger includes error tracking with a whole suite of amazing monitoring tools — all for probably less than you're paying now. Discover why so many companies are switching to Honeybadger here.
    Start free trial
    Stop digging through chat logs to find the bug-fix someone mentioned last month. Honeybadger's built-in issue tracker keeps discussion central to each error, so that if it pops up again you'll be able to pick up right where you left off.
    Start free trial