Any benefit of adding a read Query in a service class in Spring - spring

Question

There is a code where there are single read query in a service class , does this have any effect in terms of performance/internal way hibernate runs the query ? As it's easier to just write the query in a facade/handler layer than a call the service class in read only ops
Run with hibernate here and PersonRepo is the envers class for the Person class annotated with #Entity
For eg)
#Transactional(isolation = Isolation.READ_COMMITTED, propagation = Propagation.REQUIRED, rollbackFor = [Exception::class])
#Service
class PersonService(
private val personRepo: PersonRepo
) {
fun getPersonById(personId: Long): PersonEntity {
return this.personRepo.findById(personId)?: throw ValidationException("person $personId does not exist")
}
}
when writing this query in handler/non service layer when should we
call it from a service class
#Component
class PersonHandler (
private val personRepo: PersonRepo,
private val personService: personService,
private val someOtherHandler: SomeOtherHandler
) {
fun displayPersonAge(personId: Long) {
val person = this.personService.getPersonById(person)
someOtherHandler(person)
}
}
get the object directly
#Component
class PersonHandler (
private val personRepo: PersonRepo,
private val personService: personService,
private val someOtherHandler: SomeOtherHandler
) {
fun displayPersonAge(personId: Long) {
val person = this.personRepo.findById(personId)?: throw ValidationException("person $personId does not exist")
someOtherHandler(person)
}
}
since both are one line here in kotlin , does adding it to a serviceClass have any benefit to it ? if it is run in a transaction/not in run in a transaction are there any effects on other db transactions and query performance under load