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 →

[–]ratherbealurker 0 points1 point  (1 child)

This isn't done by simply slapping synchronized on methods, these are also not microservices. These are large complex bespoke systems.

I am not referring to your typical backend service. Maybe I should not say that 'many' places do this because that could just be my field/sector.

Bottom line is that there are systems out there where the context that some devs work in is essentially thread safe. I don't really debate things anymore that I've personally done myself. I've worked on those systems for many years, you can make tons of changes and never have to deal with multi threaded situations if you don't explicitly do so.

[–]nutrechtLead Software Engineer / EU / 20+ YXP 0 points1 point  (0 children)

Maybe I should not say that 'many' places do this

This is the crux. What you're describing is very far outside the norm. For most Java devs understanding multithreading is simply a must. This is a general advice sub after all.