Rails Best Practices | use after_commit

Most developers use AR callbacks after_create/after_update/after_destroy to generate background job, expire cache, etc., but they don't realize these callbacks are still wrapped in database transaction, they probably got unexpected errors on production servers. A relational database, like mysql, provides transactions to wrap several operations in one unit, make them all pass or all fail. All isol

[willnet]

after_createとかだとトランザクションのコミット前に実行されてしまう可能性があって、DBの作成・更新内容を閲覧できないケースがある／after_commitつかうと安全