My views on the Repository Pattern.
It is a common mistake to consider the Repository pattern a generic “good practice”, without actually considering what it is good about it.
Archive for the ‘Architecture’ Category
The Repository Pattern
Posted: 19th June 2013 by Iulian Margarintescu in ArchitectureTags: NHibernate, Patterns, Practices, RavenDb, Repository
0
SOLID Software and Design Patterns
Posted: 15th September 2011 by Iulian Margarintescu in ArchitectureTags: design patterns, OOP, SOLID
Phil Japikse explains SOLID software principles – Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion- and how to apply them using design patterns.
Avoid a Failed SOA (by Udi Dahan)
Posted: 14th September 2011 by Iulian Margarintescu in ArchitectureTags: pubublish, SOA, subscribe, Udi Dahan, video
Great presentation, that I recommend to anyone building applications with business value.
See the Service-oriented architecture (SOA) wikipedia for a basic description of SOA.
You should probably watch the video, think about past projects and then re-watch the video as many times as you see fit ( about 3-4 times at least 
)… Continue reading
Sequence Diagrams
Posted: 31st July 2011 by Iulian Margarintescu in ArchitectureTags: diagram, sequence diagram, uml
A very interesting service for creating Sequence Diagrams: Web Sequence Diagrams.
Sample diagram created with only a few lines of text:
The diagram above was created with the following lines of text:
AdapterService->ContentService: ImportArticle
ContentService->Essex: AnalyseArticle
Essex->ContentService: ArticleAnaysed
ContentService->ContentService: HitArticleAvailable
note right of ContentService: FollowUris
ContentService->SnapshotService… Continue reading
Udi Dahan: The Danger of Centralized Workflows
Posted: 13th July 2011 by Iulian Margarintescu in ArchitectureTags: Architecture, design, SOA, Udi Dahan, Workflow
Since I’ve heard the therm “workflow engine” a lot of times on a lot of projects i would like to present a new article by Udi Dahan describing the dangers of using centralized workflows.
The main touted benefit of these workflow-centric architectures is that we don’t have to change the code of the system… Continue reading