Recovering an anemic domain model into a multitier architecture
I have spent the past several days learning about domain driven design and attempting to apply it to a current project. I decomposed the problem domain into the canonical logical components: domain, infrastrucutre, and presentation. Having completed a first pass, I stepped back and realized that the architecture I created resulted in virtually all of the business logic being contained in the application services, which is the tell-tale sign of the anemic domain model code smell. After further consideration, domain driven design may not be the correct fit for my application, and even if it is, given the small number of business logic rules in my application, the layering overhead may not be worth it. Since I have only written UML and psuedo code I haven’t invested too much time and effort, but I would like to leverage what I can if it’s possible.
Modular enterprise architecture using MVC and Orchard CMS
I’m making a large scale MVC application using Orchard. And I’m going to be separating my logic into modules. I’m also trying to heavily decouple the application for maximum extensibility and testability.
Should I organize my folders by business domain or by technical domain?
For example, if I’m using some MVC-like architecture, which folder structure should I use:
Should business services cross bounded contexts?
Firstly, I am following the convention that a bounded context is synonymous to a department, or possibly one department has 1 to many bounded contexts.
PyQt application architecture
I’m trying to give a sound structure to a PyQt application that implements a card game. So far I have the following classes:
Should I create repositories with special functions like getStaffActive()?
I have seen lots of articles but none really help me. That is because I want to use dapper as a DAL. Should I create repositories with special functions? Like getStaffActive()?
Help identify the pattern for reacting on updates
There’s an entity that gets updated from external sources. Update events are at random intervals. And the entity has to be processed once updated. Multiple updates may be multiplexed. In other words there’s a need for the most current state of entity to be processed.
Help identify the pattern for reacting on updates
There’s an entity that gets updated from external sources. Update events are at random intervals. And the entity has to be processed once updated. Multiple updates may be multiplexed. In other words there’s a need for the most current state of entity to be processed.
Why make the login page to a single page application a separate page?
I am wondering why it seems to be popular to have the login page of an SPA be a separate page that is not part of the SPA (as in loaded and send data through ajax requests)?
What are the PHP web server architecture components and the purpose of each one of them?
Given below is an image of a basic PHP web server architecture: