I have a couple of questions of handlers and service-classes.
What is the difference between the two? From one post i understood that there isn't any. If so why the separation?
The handlers seem to contain only CRUD operations and validations. Is this the role of a handler? If I would add a class lets say Messaging and it would be responsible for sending messages, would it be okay to make it into a handler. Would it follow the architectural guidelines?
When creating handlers the goal is to make them as loosely coupled as possible. But as the application grows you end up having handlers with a lot of dependencies and they act like facades, How wold this be implemented according to project silk guidelines? Is it acceptable that a handler has many dependencies or would it be better to create a facade layer?
What is the difference between the two? From one post i understood that there isn't any. If so why the separation?
The handlers seem to contain only CRUD operations and validations. Is this the role of a handler? If I would add a class lets say Messaging and it would be responsible for sending messages, would it be okay to make it into a handler. Would it follow the architectural guidelines?
When creating handlers the goal is to make them as loosely coupled as possible. But as the application grows you end up having handlers with a lot of dependencies and they act like facades, How wold this be implemented according to project silk guidelines? Is it acceptable that a handler has many dependencies or would it be better to create a facade layer?