[REQUEST] Any plan to refactor those huge classes?

I don't know whether DeepSpeed is planning to do large refactor, if not, below is my suggestion.

Is your feature request related to a problem? Please describe.
Thanks for this great project, DeepSpeed is wonderful incredible powerful.
But i found its python codes full of large even huge classes, as DeepSpeed turned more powerful, classes become larger and hard to read or maintain.

Describe the solution you'd like
I think Instead of adding more new features, it is better to do more refactor, or in the near future, DeepSpeed will be hard to maintain, hard to debug or add even little new feature.
DeepSpeed is mainly manipulating data/weight, if refactor it by DOP(data oriented programming), the code should be much better to read and maintain.
There is a good book of data oriented programming: https://livebook.manning.com/book/data-oriented-programming/chapter-1/v-13/

Describe alternatives you've considered
DOP can live with OOP, so refactor can go on many steps.
Or just refactor the large classes to smaller modular classes should be also great.
I found fairscale(https://github.com/facebookresearch/fairscale) has similar functions with DeepSpeed, but its codes are much simpler.

The issue does not name files, classes, tests, or an entry point. Start by surveying the large Python classes in DeepSpeed and comparing the relevant areas with FairScale, then establish a specific refactoring scope and acceptance criteria. Done would require an agreed, modular refactor rather than a general proposal.