💎#Rails tip💎 `after_destroy` callback isn't safe for deleting external (API) things. On exception raise, the transaction will rollback but you still lost your external thing. In that case, use `after_destroy_commit` to be sure the transaction has finished. #ruby #rubyonrails

@websebdev Not sure if model callbacks are the right place to trigger external APIs. A service that „decommissions“ an entity with all the necessary business steps seems more desirable to me. What do you think?

@websebdev If you have to reflect things like this onto external APIs, a great way to do this, is by publishing lifecycle events upon which your app can react. Kafka can be really useful for that.

@websebdev Sidekiq jobs can ensure that your network calls go through when you do use after_commit

@websebdev `after_commit` is the key to doing all that stuff in a separate worker which handles the errors and exceptions.

@websebdev And if the external thing raises? 🙂