A modern programming language that makes developers happier.

kotlinlang

Hi everyone, I have a question about `Dao/Repository` in Kotlin. Some Github projects like <https://github.com/mvysny/vok-orm> and <https://github.com/JetBrains/Exposed/> use the DAO approach defining data access methods on the entity using a companion object, while, generally, in Java(i.e. Spring Data) we use Repositories to access the data. What is your opinion? Why one approach is better than another?

Dao / Repository are not Kotlin specific concepts. Some good reads: <https://martinfowler.com/eaaCatalog/repository.html>
<http://blog.sapiensworks.com/post/2012/11/01/Repository-vs-DAO.aspx>
<https://stackoverflow.com/questions/8550124/what-is-the-difference-between-dao-and-repository-patterns>

See <https://github.com/JetBrains/Exposed/issues/24> and <https://spring.io/blog/2016/03/20/a-geospatial-messenger-with-kotlin-spring-boot-and-postgresql> to get more details about why I prefer the repository approach.

Thanks <@U0BUH9FRD>, after I’ll read with attention. Looking around I found this link <http://mavi.logdown.com/posts/5771422> where there is some reason about this choice. TL;dr, avoinding dependency injection.