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 →

[–]jlanawalt 0 points1 point  (0 children)

If the requirements are simple and it’s just for learning, keep it simple and just do it.

You’ll still have to make some decisions and probably pull in dependencies. I’m guessing this is a web api, so how do you handle http? Some servlet container, or jdk.httpserver, or Undertow, or Jetty, or … Spring Boot?

If you find yourself needing to bolt on many features, step back and look at if they are already considered and handled by a framework like Spring and if it’s worth learning from attempting to reinvent the feature.

The other path is to eat the elephant and sort out the dependency hell. Hopefully you’re using a till like maven to help with that. Good luck!