Rationale

Why should this feature exist?
The order of loading resources is Databases → Thread Pools -> Network -> Consensus → API, the order of releasing should be reversed, API → Consensus -> Network -> Thread Pools → Databases.

Implementation

Do you have ideas regarding the implementation of this feature?
As mentioned above.

• The lifecycle of Databases is managed by the spring container. Tune the databases closure #5428
• Thread Pools are initialized with beans.
• Application. startup: Network-> Consensus -> API.
• Application.shutdown: API → Consensus -> Network -> Thread Pools.

Are you willing to implement this feature?
Yes.