API in Spring Boot Repository vs DAO : <p>I'm trying to design an rest API in spring boot and what to ask about a few design decisions. I am completely confused by the whole difference between DAO vs Repository pattern/design. After hours of reading I still don't really understand the difference between the two or which one is preferred standard for designing API's that make backend connections. </p>

<p>Here's a simply UML diagram to highlight the high level view of the api:
<a href="https://i.stack.imgur.com/JYLQE.png" rel="noreferrer"><img src="https://i.stack.imgur.com/JYLQE.png" alt="enter image description here"></a></p>

<p>This is how I understand a good architecture of an API. But then I came across <a href="https://thinkinginobjects.com/2012/08/26/dont-use-dao-use-repository/" rel="noreferrer">this article</a> using repository pattern instead of dao with a specification design. I don't understand why a dao interface can't just have a <code>query</code> function? Does that break the idea of what a DAO is or something?</p>

<p>My question is: what's the best standard to use in today's day in developing an API in Spring Boot and Java 8</p>
