Row Level Authorization with Entity Framework
A few posts back I wrote about the benefits of having a well encapsulated data access implementation. One of the benefits outlined there was the advantage
Data Isolation and Sharing in a Multitenant System - Part 3
This is the last part of the "Data Isolation and Sharing in a Multitenant System" article, which is also a continuation of my post
Data Isolation and Sharing in a Multitenant System - Part 2
This post is the second part of the article that shows how a well encapsulated data access implementation can play a key role in implementing a
Data Isolation and Sharing in a Multitenant System - Part 1
In the previous post I've shown few of the additional benefits a well encapsulated data access implementation brings. Implementing multitenancy is one of them. This article
Benefits of Data Access Encapsulation
We all know that achieving a good Separation of Concerns is good, because it increases the maintainability and it reduces the cost of changing our code.
Unit Testing on Top of Entity Framework DbContext
When writing unit tests one of the challenges is to isolate your tests from everything. To isolate them from the code that is not in their
Repository Implementations
In my previous post I have presented a way to separate your data access from the business logic, when a relational database is used. I have
Separating Data Access Concern
In our days most of the applications that have a relational database as storage, use an ORM to access the data. The ORM (Entity Framework, Hibernate,
Founder and Partner
Partner
Recent posts
- Why Programmers Should Challenge the Stakeholders
- Migrate to Ghost 1.x on Azure
- Decide between In-Process or Inter-Process Communication at Deploy Time - Part 3
- Decide between In-Process or Inter-Process Communication at Deploy Time - Part 2
- Decide between In-Process or Inter-Process Communication at Deploy Time