Hasor itself is a framework system composed of multiple different series of frameworks. The capabilities of these subframes cover IoC, Aop, WebMVC, databases, and other aspects. The basis of all this is due to Hasor's plug-in capabilities.
Hasor helps you design better APIs, and its unique framework extension capabilities allow new capabilities to be fully seamlessly integrated into a unified API system. We built common features that enable you to extend Hasor instead of adding every feature to the core framework.
Hasor's expansion ability is more like an interface for a LEGO toy, and anyone can provide LEGO bricks in a very simple way and then blend them together easily. During the use process, I can't feel that behind it is the collaboration of multiple different frameworks. The Hasor API itself is a good example.
Hasor's goal is to make development and debugging easier and faster, rather than more difficult and slower.
For an introduction to Hasor and use, please check out our user guide. We have been updating and iterating since open source in 2013, and now it has been almost 10 years since many key applications are running Hasor, and now you can use it with more confidence. We hope you like it as much as we do.