Confused on how to properly employ a Repository Pattern with Service/Business Layer on top
I’m building a ASP.NET Web Api 2 solution for learning purposes, and I’ve hit a snag. I was wondering if anyone could tell me what exactly it is that I’m missing.
Repository pattern implementation that knows nothing about the database table and column names
I’ve seen around the Internet and Github, implementations for the design pattern Repository that knows about database table and column names. I was think, if I want to work with the database as a plugin, that I can unplug and plug another respecting Open/Closed for the rest of my code, my repository should not know about the column names of the database I’m using. So how to implement this pattern in a way that it can transform the result from the database into a Entity of my domain, without knowing about the database table and column names?
Repository pattern implementation that knows nothing about the database table and column names
I’ve seen around the Internet and Github, implementations for the design pattern Repository that knows about database table and column names. I was think, if I want to work with the database as a plugin, that I can unplug and plug another respecting Open/Closed for the rest of my code, my repository should not know about the column names of the database I’m using. So how to implement this pattern in a way that it can transform the result from the database into a Entity of my domain, without knowing about the database table and column names?
Repository pattern implementation that knows nothing about the database table and column names
I’ve seen around the Internet and Github, implementations for the design pattern Repository that knows about database table and column names. I was think, if I want to work with the database as a plugin, that I can unplug and plug another respecting Open/Closed for the rest of my code, my repository should not know about the column names of the database I’m using. So how to implement this pattern in a way that it can transform the result from the database into a Entity of my domain, without knowing about the database table and column names?
Repository pattern implementation that knows nothing about the database table and column names
I’ve seen around the Internet and Github, implementations for the design pattern Repository that knows about database table and column names. I was think, if I want to work with the database as a plugin, that I can unplug and plug another respecting Open/Closed for the rest of my code, my repository should not know about the column names of the database I’m using. So how to implement this pattern in a way that it can transform the result from the database into a Entity of my domain, without knowing about the database table and column names?
To depend on source code or on binary?
We have two in-house projects, A and B, developed by different teams with B dependent on A. Since source code for both projects is stored in git, I’ve included project A as a submodule into project B and configured the build system to build both in right order. An alternative solution would be to consume A via a binary repository manager such as Artifactory or Nexus.
Commercial Apps with an Open Source on github [closed]
Closed 9 years ago.
How to organize repository branches? [closed]
Closed 9 years ago.
Is this a valid implementation of the repository pattern?
I’ve been reading up about the repository pattern, with a view to implementing it in my own application. Almost all examples I’ve found on the internet use some kind of existing framework rather than showing how to implement it ‘from scratch’. Here’s my first thoughts of how I might implement it – I was wondering if anyone could advise me on whether this is correct?
Should I have separate units of work for each EF bounded context?
I have some EF bounded contexts like follows