I've built both models (and more too) over decades.
There are lots of questions one might ask before deciding between these two (or other) approaches:
* Where does this team want the boundary between client and server in terms of user experience, server load and substantial UX interaction latency?
* Can this frontend team independently plumb a changes all the way through the database?
* Are backend teams always available for (or interested in) every minor update?
* Are both halves of the application deployed on the same schedule?
These are a handful of the first questions I'd ask before trying to push either solution at this point in time, the answers would likely lead to more questions.
There are lots of questions one might ask before deciding between these two (or other) approaches:
* Where does this team want the boundary between client and server in terms of user experience, server load and substantial UX interaction latency?
* Can this frontend team independently plumb a changes all the way through the database?
* Are backend teams always available for (or interested in) every minor update?
* Are both halves of the application deployed on the same schedule?
These are a handful of the first questions I'd ask before trying to push either solution at this point in time, the answers would likely lead to more questions.