Last Updated: 2024-04-18

Imagine you have the following structure:

controller -> model -> paypal (e.g. hits api through a method here)

This is a bad design because an ActiveRecord model should only be responsible for talking to the DB. It should not be responsible for API stuff wtih PayPal.

A better design would be:

controller -> orchestrator/service -> [paypal_api, model]

In what ways is this better?

• No need to get in place the constellation of associated records in a test of the API
• No need for DB or to boot Rails when testing PayPal api stuff