New answers tagged

2

I don't think there is a compelling reason why combining the data transfer in a single request needs to violate the SRP: the server or backend will provide an API which returns a complex object, which may consist of data and meta data like descriptions creating and filling that object might be split up to into different tasks, with different functions on ...


1

Most people who complain about “two responsibilities” have severely misunderstood what is meant by “responsibility”. If you go to the gym, you can be sure the person who checks your membership is going to be the one signing up new customers. That’s because the responsibility is: Make sure that once your code is done, either the user is signed in, whatever ...


1

The role of the interactor or use case object in clean architecture is to model the flow of logic for that specific use case, or as Uncle Bob puts it, "control the dance of the entities". That is a single responsibility regardless of how many steps are involved. A responsibility in this context is typically defined as a "reason to change",...


0

The original question sounds like there is a problem with in-memory objects changing frequently does not work well with the visitor pattern. If your visitor was implemented as a pure function and the system scaled properly with parallelization this could scale infinitely. However I don't think this is what you are asking. It sounds more like you are asking ...


Top 50 recent answers are included