You can opt not to use the organization service context and replace it with the organization service proxy instead, which will simplify the implementation. Nevertheless, this recipe highlights the repository pattern and how to use it.

The advantage of having a separate class for your data access layer is that you can alter its internals without affecting the consumer, as we will observe in Replacing your LINQ data access layer with QueryExpress recipe of Chapter 6, Enhancing Your Code; a perfect example of object-oriented encapsulation at its best.