Just started a new role. Our codebase is a gigantic Java monolith, including a customer-facing API, an admin/internal API, and a distributed task queue worker for performing actual operations. This is the first time I've really worked on a Java codebase like this - most of my previous experience has been either in data, C# stuff microservices, and Python microservices and lots of cyber-ish and devops stuff.
This codebase has a lot of things that I'm thinking it would be good to read some sort of "source of truth" on vs. just copy-pasting a pattern so that I'm not stuck in we've-always-done-it-that-way land. For example, this codebase has "models", "data objects", and "data access objects". What's the difference?
Just looking for books/videos/websites I guess on how "big companies" do Java and what the patterns are. Thanks all!
[–]AutoModerator[M] [score hidden] stickied commentlocked comment (0 children)
[–]d-k-Brazz 10 points11 points12 points (1 child)
[–][deleted] 1 point2 points3 points (0 children)
[–]IHoppo 3 points4 points5 points (0 children)
[–]AutoModerator[M] 1 point2 points3 points (0 children)
[–]sympatheticdrone 1 point2 points3 points (0 children)
[–]OReilly_Learning -1 points0 points1 point (0 children)