Then you just need to initialize the manager at the appropriate place in the viewController, and then load the tableView. The advantage of this method is that if you use the same management logic in many places, the code can be split very well.
If you just want to reduce the number of rows of viewController, and this management class is not suitable for each viewController, then there is another method, which is also good.
This is actually a question of how to split a very large source code.
Here are several methods recommended to you, all of which are better.
1. Independent datasource, delegate management class
Then you just need to initialize the manager at the appropriate place in the viewController, and then load the tableView.
The advantage of this method is that if you use the same management logic in many places, the code can be split very well.
If you just want to reduce the number of rows of viewController, and this management class is not suitable for each viewController, then there is another method, which is also good.
2. Use category to split files
There is no one-size-fits-all solution, just find one that suits you.
Both = your new class, just implement the protocol method in the new class