|
|
|
|
|
|
by sbov
3322 days ago
|
|
|
We do roughly this where I work, so I broadly agree. That said, it's fairly common for the unit of reuse to be below service methods. Also, depending upon how exactly you manage transactions, another thing to look out for is making multiple non-idempotent service calls from the view - this will be an area ripe for race conditions you likely aren't testing. |
|
|
In terms of utility functions or serializers? What does that look like exactly?
E.g. in our codebase service methods can call helper methods (non-reusable), utility methods (reusable), and serializers (non-reusable).