Some patterns I’ve usually encountered while working code bases written by .net developers. You can also read more on msdn.
Usually you find classes with postfix name like:
customerContext.Save()to persist changes to objects.
People are often confused by “Unit of work” also mentioned in connection to these patterns. Many OR-mappers implement the repository pattern. Popular libraries include Entity Framework, NHibernate and RavenDB (library and database).
The key point of DDD is ubiquitous Language. Being able to have roughly the same type of concepts as the users can be very helpful.
This type of architecture is quite simple. The main benefit of it is that it’s easy for people to grok. This type of architecture is not as popular anymore because it increases the amount of code you have to write.
In this type of architecture it’s not uncommon to have an additional layer in the database implemented by stored procedures.
Provides a way to lower cohesion between components. Can also be helpful if you want to distribute work.
Do you want to send a comment or give me a hint about any issues with a blog post: Open up an issue on GitHub.
Do you want to fix an error or add a comment published on the blog? You can do a fork of this post and do a pull request on github.