in spring, should there always be a layer between controllers and repositories? what do you think?

# announcements

[Bruno_]

in spring, should there always be a layer between controllers and repositories? what do you think?

[x80486]

It's a common practice to do that so you can isolate behaviors...but it's not strictly needed

[Sergey Bondari]

depends on complexity of that layer between

[Bruno_]

@Sergey Bondari almost none, all it's doing is to call the repository

[Bruno_]

for now I've kind of merged the repository and controller into one class, exmaple class looks like this

@RestController
public interface FieldOfStudyRepository extends JpaRepository<FieldOfStudy, Long>
{
    @Override
    @GetMapping("/fields")
    List<FieldOfStudy> findAll();
}