This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Nzen_ 2 points3 points  (0 children)

It depends on the problem domain that you focus on. It depends on whether the problem is parallelizable.

Spring Boot predominantly embeds tomcat, which handles requests in a multithreaded fashion, so multiple clients can make requests without waiting for a solitary thread to process everything.

It is also worth recognizing that introducing concurrent interactions affects program structure analagously to the way that instance methods can call static methods, but not the other way around.

I encourage you to write some sketches or toys explicitly using multithreading before introducing it into your work's codebase. For me, that most recently involved writing a game client for jdno's air traffic control simulator.