Java hot deployment and hot loading
1 Compile/deploy projects without restarting the server
2 Java-based class loader implementation
Difference:
Hot deployment:
Deployment method: Redeploy the project when running the project (save time, package and replace directly)
Implementation principle: Load the entire application directly (release memory, more time than hot loading, but clean)
Usage scenario: Production environment
hot Loading:
Deployment method: Reload the bytecode file of the class when running the project.
Implementation principle: Start a background process when the container is running to detect changes in the class, and reload the class if there is a change.
Scenario: Development environment ( Faster and more convenient) Directly modifying class files is not safe and will not leave logs and other records, but it will be much more convenient if it is just a development environment. It is common for us to restart services frequently in our usual development, saving a lot of time after hot loading.