One xsodata file for a business need will be a suggested method always .
--All Services in ONE XSODATA File
-->less readability , huge metadata will be generated, all objects will be activated in change of file.
--> one odata model will be required to consume from ui5 or any such ui services
- XSODATA Files per Business Object
-- >for a particular business use, we can keep one file . It will have separated odaata models per file, better readability
- 1 XSODATA File per table
--> not at all required. separate metadata will be generated for each of these files, which is not required at all