Dofactory has a 3.5 framework for developing software and includes some design patterns which are explained in a document. There's a sample app built using the framework which has user interfaces for WinForm, WPF, ASP.NET (WebForms), ASP.NET MVC, plus DAL's using Linq & ADO.NET which makes it a candidate for a learning tool and a framework to be used in real world apps.
the framework was good, in the sense that i was able to get to grips with what goes where. I liked how it included some of the PEAA patterns. I would be very interested how the MVC and WPF clients have been implemented.
It looks like a compilation of already existing documentation. There already are some excellent books about design patterns and .Net. In addition to that, they use "LINQ-TO-SQL" for their DAL, which is already dead.It looks like their framework is not up to date anymore...
The client I work for purchased this. It's Usefull but it's not a framework that you can use so that your application is using Design Patterns, it's more like an example of how to solve programming problems using design patterns. If you want to learn Design Patterns. I recommend the book "Head First Design Patterns". It's using Java as the programming language, but the concept is the same. The very best thing of this book is that it's readable, not the dry theory of Fowler. I find it very usefull
anti-patterns · application api · application architecture · architecting · architecture documentation · dark energy and dark matter · deployment · development · devops · docker · implementing commands · implementing queries · inter-service communication · loose coupling · microservice architecture · microservice chassis · microservices adoption · microservicesio updates · multi-architecture docker images · observability · pattern · refactoring to microservices · resilience · sagas · security · service api · service collaboration · service design · service discovery · service granularity · service template · software delivery metrics · success triangle · team topologies · transaction management · transactional messaging
I do not claim that this design is in any way better or cleaner than any others out there. This is simply what worked very well for me in several of my projects. Most software developers out there recognize that there is no single architecture that is best. The best architecture is the one that works well for you, your team, and your type of project. This is by no means a production-ready solution, it is not a framework, it is merely a starting point. 2b1af7f3a8