Reuse the data CRUD methods in data access layer, but they are updated too quickly
I agree that we should put CRUD methods in a data access layer， However, in my current project I have some issues.
Questions about identifying the components in MVC
I’m currently developing an client-server application in node.js, Express, mustache and MySQL. However, I believe this question should be mostly language and framework agnostic.
Stop myself from over-complicating applications
Recently I worked on a fairly large project involving C# and MVVM. This application had around 160 projects in the solutions each seprarated into their own layers. As I have been working on this application for almost a year, building it from scratch as part of a team, I am now coming off that project and onto smaller more trivial projects.
What is the best way to diagrammatically represent a system threading architecture?
I am yet to find the perfect way to diagrammatically represent the overall threading architecture for a system (using UML or otherwise).
Motivation for a service layer (instead of just copying dlls)?
I’m creating an application which has 2 different UIs so I’m making it with a service layer which I understood is appropriate for such scenario.
Accessing Repositories from Domain
Say we have a task logging system, when a task is logged, the user specifies a category and the task defaults to a status of ‘Outstanding’. Assume in this instance that Category and Status have to be implemented as entities. Normally I would do this:
Futures/Monads vs Events
In an application framework
when performance impact can be ignored (10-20 events per second at max),
what is more maintainable and flexible to use as a preferred medium for communication between modules – Events or Futures/Promises/Monads?
Should I use a workflow engine?
I need to add some new features to a PHP application. It is to follow the steps of a order. A process create some orders, the order goes to confirmation, then if approved is sent to a provider, later the provider confirm that can deliver the order, a request is made to the provider and so on…
When is a Use Case layer needed?
In his blog post The Clean Architecture Uncle Bob suggests a 4-layer architecture. I understand the separation between business rules, interfaces and infrastructure, but I wonder if/when it’s necessary to have separate layers for domain objects and use cases. What added value will it bring, compared to just having the uses cases as “domain services” in the domain layer?
Is having functionality in DB a road block to scalability?
I may not be able to give the right title to the question. But here it is,