If you are talking about what I think you are talking about, then this is an interesting discussion.
Technically, since setFirst()it is getFirst()not synchronized, then it is possible setFirst()to introduce one object into Thread 1 and getFirst()to return another object to Thread 2. Memory The Java model reserves the right to make this "ultimately consistent," as they say.
, Spring, bean ( ), , HTTP- () , bean, - .
: . HTTP- Spring, Java , .
( , , ). - , .
, .
, , . .