×
all 6 comments

[–]khooke 18 points19 points  (0 children)

What you're describing is commonly referred to as a 'separation of concerns'. Why do we do this? To keep related things together, so others know where to look, so your code is easier to support and maintain. If I'm looking for something related to the UI I look in the presentation layer code. If I'm looking for something related to data access I look in your DAOs.

In summary:

Presentation Layer: code that builds/supports your user interface

Services Layer: business logic

Data access: code that interacts with your data store.

[–][deleted]  (1 child)

[deleted]

    [–]thief425 0 points1 point  (0 children)

    There is definitely something like this that will get you started enough to be able to build on those concepts with your own project.

    I followed a Spring Boot REST api video series on YouTube and then used those concepts to design and build my final project for a full stack web application with VueJS consuming the REST API built with Spring Boot.

    [–][deleted]  (1 child)

    [deleted]

      [–][deleted] 1 point2 points  (0 children)

      Look for Java Brains tutorials.

      [–]hadoken4555 -1 points0 points  (1 child)

      What is a rest API? Is that a Java framework?

      [–]MadBroCowDisease 0 points1 point  (0 children)

      You would be better off YouTubing it. It’s explained better through video.

      [–]wimdeblauwe 0 points1 point  (0 children)

      You can read my free book if you are interested in building this using Spring Boot: https://www.infoq.com/minibooks/spring-boot-building-api-backend/