Implement jeffijoe/awilix as container

[arkecosystem]

Implement jeffijoe/awilix as container

[faustbrian]

Another big advantage of having IoC is that will be much easier to modularise the codebase which offers greater control over the whole core. An example would be that we could split the parts like API, database, logging, etc. into modules which creates better separation of concerns and reduces the size of the installation on relays and things like raspberrys.

• arkecosystem/core-database-sequelize
• arkecosystem/core-public-api
• arkecosystem/core-winston-logging

Now we could register those packages in the container like container.register('database', require(config.database.driver)) where database.driver would be @arkecosystem/core-database-sequelize.

If I wanted to use my custom driver faustbrian/custom-db-driver I would just pull in that package, set the driver to faustbrian/custom-db-driver and if I adhere to the database interface the application should just continue to work because the IoC bound the faustbrian/custom-db-driver to the container.

[faustbrian]

Also testing will be much easier & cleaner if we split all the sections of the core into modules because each module will only contain tests that are related to the module itself.

[fix]

Well debugging IoC is always a bit of a nightmare, and my experience with Java IoC was pretty bad when i started hardcore optimisation for reading satellite images.

On blockchain, we don't have much need in making the best architected software for the backend, the reason is the tradeoff to have fast optimised way to deal with data stream.

We are not like a CRM software handling complex interactions between processes. We have a extremely simple design (blocks transactions and peers) to deal with in the most optimised way.

I may be wrong but IoC looks over engineering here