I think this is something that heavily depends on your use case, but in general I would just stick to typical Object-Oriented Programming best practices (e.g. SOLID) and try to aim for a level of abstraction that fits your application. If your different integrations use the same types of information, then having them reuse the same message classes makes sense to me.
- Log in to post comments