eShopOnWeb Architecture (7/16) – encapsulates navigation collections so consumers can’t edit them directly

Another example of encapsulation but this time on the navigation collection level is seen in eShopOnWeb with the use of IReadOnlyCollection.

We can see below that the _items collection is private so no potential consumer of the basket class can manipulate this collection directly and potentially bypass the business logic.

The Items collection on the other hand is exposed as an IReadOnlyCollection which acts as a in-synch (changes to the underlying collection are reflected in the IReadOnlyCollection) wrapper around the main _items collection.

Click on the image for a larger view in a new window…


You might also be interested in...

eShopOnWeb Architecture (6/16) – uses private setters and non default constructors to support encapsulation which helps keep the model valid
eShopOnWeb has some really nice examples of encapsulation. The particular example below is the CatalogItem class. Click on the image … Continue reading eShopOnWeb Architecture (6/16) – uses private setters...

eShopOnWeb Architecture (9/16) – uses the Aggregate root pattern to ensure child objects are not manipulated out of context
Aggregate roots are a central concept in Domain Driven Design. The idea is pretty simple and refers to how certain entities … Continue reading eShopOnWeb Architecture (9/16) – uses the Aggregate...

eShopOnWeb Architecture (8/16) – uses in memory caching to avoid sending unnecessary queries to the DB
To improve performance eShopOnWeb uses IMemoryCache to implement in memory caching to prevent queries being sent to the Database for … Continue reading eShopOnWeb Architecture (8/16) – uses in memory...

eShopOnWeb Architecture (14/16) – uses parameterized tests
I love parameterized tests. Instead of adding many different test methods with different inputs set in the method body we … Continue reading eShopOnWeb Architecture (14/16) – uses parameterized tests...

eShopOnWeb Architecture (16/16) – uses clean architecture
On a high level eShopOnWeb uses clean architecture. The main idea of clean architecture is that the solution is spilt … Continue reading eShopOnWeb Architecture (16/16) – uses clean architecture...

One thought on “eShopOnWeb Architecture (7/16) – encapsulates navigation collections so consumers can’t edit them directly”

  1. Pingback: eShopOnWeb architecture article series (16 parts)

Leave a Reply

Your email address will not be published. Required fields are marked *