Timeline for Is it problematic to have a dependency between objects of the same layer in a layered software architecture?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 4, 2019 at 12:02 | vote | accept | bracco23 | ||
| Mar 23, 2019 at 7:57 | comment | added | Doc Brown | @bracco23: the pros and cons of having "inner" dependencies are the same as the pros of cons of having arbitrary dependencies. "Cons" are they make components harder to reuse and harder to test, especially in isolation from other components. Pros are, explicit dependencies make things which require cohesion easier to use, understand, manage, and test. | |
| Mar 22, 2019 at 16:06 | comment | added | bracco23 | Continuing on the UI example, what are the pro and the cons of having the inner dependencies? I can see that it makes easier reuse and introduce cyclic dependencies, which might be a problem depending on the DI method used. Anything else? | |
| Mar 20, 2019 at 21:13 | history | edited | Doc Brown | CC BY-SA 4.0 |
added 134 characters in body
|
| Mar 20, 2019 at 17:52 | history | answered | Doc Brown | CC BY-SA 4.0 |