Question: What's the difference between a repository and a service? I don't seem to grasp it.

I'm talking about data access through a data access layer, typically with linq to sql.

Very often i see repositories with simple CRUD methods, and services with more business-specific methods.

We can take [this](https://web.archive.org/web/20160702012441/https://weblogs.asp.net/rashid/shrinkr-url-shrinking-service-developed-with-entity-framework-4-0-unity-asp-net-mvc-and-jquery-part-1) blog post as an example. If you look at the interfaces at the bottom (images), he has two repositories and two services. How does one know what to put where?

As I said, repositories seems to be more for CRUD-like operations and Services more business oriented.

Answer: 
The repository is where the data is stored. The service is what manipulates the data.

In a real-world situation comparison, if your money is stored in a vault in a bank, the vault is the repository. The teller that deposits, withdraws, etc is the service.
I would say as a first try, in the general sense (until you give more context if you have one):

* a **repository** is where you place some global objects, to be used later.
* a **service** is a business logic code, made explicit (and ideally separated from the Presentation layer, and database layer ?)