If you were familiair with Eclipse you know that when you would save java class it will build automatically. With IntelliJ you don't have to spam the CTRL + S combination anymore because it will save automatically but there is only one problem. Your class will not be compiled.
Some developers prefer to compile manually because of the performance of the IDE but it can trick you into weird behavior if you forget it once. Especially when developing microservices where you are running 5 instances of IntelliJ.
IntelliJ has the option to build project automatically, BUT it only works while not running / debugging. How sad that is.
I was developing a Spring Boot application using Spring Boot Developer Tools which comes with a neat feature where classes are being reloaded. The dev tools only restarts the ServletContext within seconds. The main problem was that it only happens when the class is being compiled. So in Intellij you had to trigger a build yourself while in Eclipse when you would save your class, it will compile automatically even when running.
In IntelliJ it is possible to override this behavior to build automatically even when the application is running.
Keep the description in your mind in case you get into weird behaviour.
Close and now you are done.
TCPMon is a good TCP/IP tool to intercept the traffic that is being passed and shows the payload of the traffic. Sometimes when you are passing a cookie, or some other meta data you want to be sure if everything is being passed correctly. The tool also allows to simulate a slow connection. Which is ideal to reproduce timeout and/or performance issues.
TCPMon is not supported anymore but it is still one of the most populair tools out here. If you have a better alternative, feel free to mention them.
You can install TCPMon in IntelliJ as a plugin and it will appear in your toolbar.
Now when you make requests to port 8081, it will redirect to 127.0.0.1:8080. You will see the following output