Home/ Questions/Q 5850457
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-22T13:08:35+00:00

I am relatively new to developing Cocoa applications on the Mac and come from

  • 0

I am relatively new to developing Cocoa applications on the Mac and come from a .NET C# background. I was wondering if a Cocoa Model object should contain its own data access methods such as Create, Update and Delete etc. Apples documentation seems to lean towards the Model doing everything but it doesn’t seem right to have a Model (ie UserModel) which has a method named GetUsers which returns a collection of UserModels!

In ASP.NET MVC all my Models are just a representation of a Business object (ie a User) or a View. Using the example from above it would be the controllers responsibility to call a service (Business Layer or something of that nature) and get back a list of UserModel objects. The same controller would also populate a UserModel with data and pass that as a parameter to some other service which could then perform an Update or a Delete.

Any thoughts on this subject would be greatly appreciated as example code from Apple tend to be rather simple and don’t really touch on CRUD type operations.

Thanks in advance.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I also come from a .NET background and I agree that Apple sometimes confuse things a bit. I tend to keep my domain models clean and implement a data access service. The only time I do it differently is if I am using CoreData in which my domain level objects are also CoreData objects (so they have underlying data persistence) HOWEVER I still use a Storage Service / Data Access Service to retrieve and save through.

    If you want an example of a Storage Service / DAL I use then one of my blog posts contains it….CoreData Example

    • 0