• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (1)

1 localhost commented Permalink

In response to;"So, what distinguishes a "good" architecture from a "bad" one?"Perhaps it's an overly simplistic view, but I think that an architecture that doesn't exhibit the properties required of it, in the context in which its deployed, is a "bad" architecture, while one that does exhibit those properties is "good".While I agree that the traits you've listed there are commonly found in many good architectures, I wouldn't say they were necessarily required for all contexts. For example, sometimes it is necessary to make a design decision which trades off simplicity for performance. And in such a case, the the better performing architecture may well be better for the context in which it's used, despite not being quite as simple.

Add a Comment Add a Comment