Question for gitness and drone framework

[fengxuway]

I found that after upgrading from drone code to gitness, the framework changed a lot.

There used to be a core directory responsible for defining the interfaces of all modules, and each module was organized using dependency inversion. This is the old code: https://github.com/harness/gitness/tree/drone

In the latest code of gitness, each module does not define an interface, and there are often various structure pointers during dependency injection.

I would like to ask, what are the advantages of such a structure, and what considerations did it evolve into?

[fengxuway]

Could you share your thoughts? @johannesHarness @tan-nhu @cjlee01