since the "fat event" ones are vaguely defined here, they could be arbitrarily close to or far from the "Entire object" cases. How does it differ? Maybe it does not.
Your team decides what parts of the model to expose in its events and it becomes an API in its own right.
You might change the names of fields, move them to places that don't reflect where they live on a nested model, etc. It requires a lot more thought and maintenance.
That isn't to say the choice can't be correct. All of these approaches have pros and cons.
You might change the names of fields, move them to places that don't reflect where they live on a nested model, etc. It requires a lot more thought and maintenance.
That isn't to say the choice can't be correct. All of these approaches have pros and cons.