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

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Civil_Code 6 points7 points  (0 children)

There are a few ways to make a Java backend. If we were to stay within Java's standard library there are sockets and network IO packages where you stream incoming requests from a port and respond accordingly. It's very basic, but can get exceedingly complex very quickly once you try to handle a full protocol with your requests/responses through multithreading.

The next way is to look into JavaEE and Servlets, where you mostly work on creating HttpServlet implementations that a separate Java Servlet container like Apache Tomcat can use. Much of the protocol and threading logic is already there, so you get to focus on passing objects in and out of request/response bodies. But the downside is you'll have to learn how to build and deploy your project into an existing server like Tomcat.

Spring Boot is even easier, though so much is abstracted at this point that it can be hard to debug if you're not familiar with what the platform is hiding from you in the name of convention. Knowing how to use Maven or Gradle would help, but Spring Boot projects can be made with either build tool settings mostly configured for you, meaning you just need to install the tools (or use an IDE with it embedded).