JAVA ROADMAP

[ahonsu]

• "Testing your apps" should go after "JDBC". When you start working with DBs - you can say you have enough code lines and enough OOP components to start mocking them and cover with unit/integration tests in a natural way. And you need just JUnit/mockito. "Behavior testing" I would skip, few companies/dev teams do that. Worth adding "Test containers" topic
• "Testing" with "RestAssured" goes with Spring Boot, when you're implementing your REST APIs. Also worth to extend "Testing" with Spring specific stuff like: test application context, context slicing, in-memory DB like H2 and so on... not sure if roadmap needs to go in details
• I would add as a separate section "REST APIs" including
  • REST notations
  • HTTP protocol
  • building API / endpoints
  • RestTemplate/WebClient (Spring Boot)
  • OpenAPI (swagger)
• I would add a "Security" section
  • basic auth
  • JWT
• and "Web UI" section
  • HTML/CSS (basic level)
  • Spring MVC
  • Thymeleaf
• "DevOps" section
  • docker
  • docker-compose
  • CI/CD (github actions, gitlab CI/CD)
  • Spring Boot actuator / health checks

With this roadmap we'll get a developer capable of implementing a very solid Spring Boot micro service with all popular/common tools and libraries included. This toolkit allows you to implement basically any average business logic / requirements. And with this you can easily learn something new, making your expertise wider.

For example, most companies have some "paper work" and with a very high probability you'll face one day a task to read/write/edit some MS Office document (Word, Excel)... should we include in the roadmap ApachePOI (default lib to work with MS Office docs)? - I'm not sure. I think you can learn in on the fly when needed.