If you use it as a global variable, you can only use StringBuffer, because spring mvc is not thread-safe. If it is only used as a local variable, use stringBuilder. The functions of the two of them are exactly the same, but the methods of StringBuffer are all synchronized methods, which improves performance under multi-threading. Worse than StringBuilder.
There is no thread safety issue when written in a method. . . Stringbuilder speed comparison, it is recommended to use it when operating large amounts of data
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
If you use it as a global variable, you can only use StringBuffer, because spring mvc is not thread-safe. If it is only used as a local variable, use stringBuilder. The functions of the two of them are exactly the same, but the methods of StringBuffer are all synchronized methods, which improves performance under multi-threading. Worse than StringBuilder.
StringBuffer thread safe
StringBuilder thread unsafe
Except for the thread problem, I think everything else is the same
There is no thread safety issue when written in a method. . . Stringbuilder speed comparison, it is recommended to use it when operating large amounts of data