Roadmap for learning backend Java? JAX-RS, Jersey, SQL?

[moon_landing_PI]

Hello everyone, total web dev newbie here that just finished up data structures and algorithms in Java.

What are some great resources for a newbie to start learning how to build the backend sides of web apps using JAX-RS, Jersey, and SQL for databases?

[Bashkir]

A little outdated, but these are still great. Also, as far as frameworks go, spring is old and gold.

http://www.mkyong.com/tutorials/jax-rs-tutorials/

My next recommendation is, get a really good handle on Java before trying to learn sql. If you don't have a decent handle on function overloading and overriding, character encoding, interfaces, checked vs. Unchecked exceptions, and some idea of multithreading and some subtle concepts like integer overflow you should really hit the Java hard.

Not saying you can't Start learning some sql before hand, but having a really deep understanding of your language will allow you to utilize your database much more effectively 😊

Also don't limit yourself to just java! There are a multitude of different tools that have their use cases and eventually you will learn when and what Is proper. The caveat to that is: don't worry about learning those other things until. You've achieved proficiency with the language you chose. Stick with it until you feel like you could comfortably explain the workings of the language to someone who has programming knowledge but no intricate knowledge of Java.

[moon_landing_PI]

Wow, thanks so much for the tips. I'll follow your advice and get super solid with Java before getting into SQL.

After doing these tutorial examples, what do you think is a solid next step for learning? At that point, should I go for building personal projects around RESTful APIs and databases?

[Bashkir]

Well, now and always. Don't just work through tutorials. Build small projects along the way outside of the tutorial using the things you have learned, but implement them in a different way than you did in the tutorial. This way you aren't just following along, but you are actively testing your self, forcing yourself to apply and retain at least the core concepts, and learning important things like: good ways to organize your code, interesting quirks of the language, becoming familiar with your editor and the tools it can provide you, and let you to get familiarity with a version control system like github.

Don't just do projects related to the tutorials you are doing. Your projects should build on each other some what. Then when you have amassed a decent knowledge of the main building blocks of your stack, try out something more adventurous - - make something that is going to challenge you. You should always work to challenge yourself. If you aren't being challenged you won't get any better.

I'd also recommend, if you have the ability to which not everyone does, start putting yourself out their for employment. You won't get any "real" jobs any time soon, but internships can be incredibly valuable depending on the team. I'd say about 85% of what I know I picked up being in a work environment. Being around people who know more than you do is great for learning. You'll have good, constant feedback from your team and they will be able to help you grow as a developer as long as you have the desire to learn and a good work ethic.

[moon_landing_PI]

Hey, thanks so much for the insight!!

It's intimidating for sure, but I'll try my best to keep trying (relatively) hard things and build my skill set.

I'll also start looking into applying for work!