Updates
Latest Tweet
What's New?
Check out for latest innovation, a computer based training video collection
Like this Page
Software Fortresses: Modeling Enterprise Architectures Review by anonymous
Not very helpful
The book has some interesting thoughts, although it makes some claims, which i absolutely can't agree with.
1. The author first writes very theoretically. There are no real life examples and so the whole architecture is somehow just a bubble. In the beginning of the book he writes about having objects, components and interfaces inside fortresses and a few chapters later he puts computers and routers inside a fortress. In my opinion the author somehow seems to mix up quite a lot of different aspects.
2. In chapter 4 he claims, that the decision between J2EE and .NET has not a long-term impact. I think this is plain wrong, because i have never seen a company porting an application from j2ee to .Net, or vice versa (at least not short-term). If choosing a technologie does not have an long-term-impact, then how comes, that there are still so many legacy systems using cobol? In comparison to that he writes, that choosing a drawbridge technology has serious long-term influence. Well, from my point of view, changing a drawbridge is be more likely to happen, then changing the technology.
3. In chapter 4 the author writes, that is is very unlikely, that a HTML-Frontend uses the same drawbridge to comunicate with the businesslogic, than for example soap. Errrr... Providing one interface for accessing businesslogic is often seen as best practice and Gamma even has a name for it: a fasade.
4. In chapter 11 the author claims, that you should choose .NET and not J2EE if low cost is important for your project. This claim sounds absolutely ridiculous to me.
5. The book start by telling you, that no matter what you have done, your enterprise architecture is a complete mess and that you are a liar, if you don't confess...Well, not a very nice way to start a book, i suppose.
In my opinion the book lacks of:
examples, prove of concept, examples, references, examples