2 years ago

Category: api, api

James Bannister • October 21, 2020 • 3 minute read Have you ever run into scenarios where you write some code in your controller that writes a bunch of data to your database? I've often built out API endpoints that accept a big payload of data and then we write a record to the database, followed by writing a bunch of related data to this new record using relationships. Problem is, for this to all be stored correctly, your multiple database writes need to all be successful.

Database transactions allow us to stage a series of changes, use this changed data, and then persist it when we are ready.