• To: "Al Snell" <alaric@a...>
• Subject: RE: Another strong/loose decision tree node (was Re: InterestingXML-DIST-APP thread)
• From: "Leigh Dodds" <ldodds@i...>
• Date: Thu, 10 Jan 2002 17:21:27 -0000
• Cc: "The Deviants" <xml-dev@l...>
• Importance: Normal
• In-reply-to: <Pine.NEB.4.33.0201101656560.9619-100000@l...>

> So I guess this is a hybrid system; I've engineered the overall
> architecture as a modular thing over the project lifetimescale, then I
> engineer modules within it from week to week...

This is the kind of view that Martin Fowler has advocated.

http://www.martinfowler.com/articles/designDead.html

"I think there is a role for a broad starting point architecture. Such things as stating early on
how to layer the application, how you'll interact with the database (if you need one), what approach
to use to handle the web server."

...

"So my advice is to begin by assessing what the likely architecture is. If you see a large amount of
data with multiple users, go ahead and use a database from day 1. If you see complex business logic,
put in a domain model. However in deference to the gods of YAGNI, when in doubt err on the side of
simplicity. Also be ready to simplify your architecture as soon as you see that part of the
architecture isn't adding anything."

YAGNI = You Ain't Gonna Need It.

• References:
  • RE: Another strong/loose decision tree node (was Re: InterestingXML-DIST-APP thread)
    • From: Al Snell <alaric@a...>

• Prev by Date: Re: Interesting XML-DIST-APP thread
• Next by Date: Re: Web Services Best Practice, summary 2
• Previous by thread: RE: Another strong/loose decision tree node (was Re: InterestingXML-DIST-APP thread)
• Next by thread: Re: Another strong/loose decision tree node (was Re: InterestingXML-DIST-APP thread)
• Index(es):
  • Date
  • Thread