• 0 Posts
  • 22 Comments
Joined 1 year ago
cake
Cake day: October 10th, 2023

help-circle



















  • Regardless of what pattern it is, you have a clear performance need and a testable implementation. That’s a win.

    Beyond looking for a pattern, I’d look at what your doing to make sure you’re not loading a ton of extra dependencies of your know you won’t use them.

    Also, you generally want a database transacting to be one logical unit of work, that all commits or all rolls back together, if you’re combining multiple transactions is likely what you want, but be aware that you might be holding locks for longer, so you might be introducing contention.

    By the same token, make sure you’ve got records locked if you need them locked. If you had atomic updates before, or your first update locked the records you needed, you may need to lock records explicitly to keep your database consistent.