|
|
|
|
|
|
by Aeolos
8 hours ago
|
|
|
Fat services, thin routes. Try moving your business logic to a library and consume it from both your UI and API routes. That minimizes duplication and decouples your public API resolvers (with backwards compatibility requirements etc) from your private UI resolvers (which you want to evolve rapidly to optimize your UIX). That's what we did and it works pretty well in practice. |
|
|