Andrewj.comObserver
Architect
Developer
Photographer
Traveller
Writer
Reviewer
Thoughts on the World
    • Welcome PageArchitectDeveloperPhotographerTravellerWriterObserverReviewerLinks

IT Architectures and Middleware

Strategies for Building Large, Integrated Systems, By Chris Britton

Posted on 5 April 2002 by Andrew - Please share: All Addthis servicesTweet thisFacebook thisLink thisYam thisShare on Google

Summary


How do the rankings work?
Content 8/10
Readability 8/10
Presentation 7/10
Ideas 7/10
Value for money 8/10
Did it do what it said on the box? 9/10

The Review

An influential book abut the real problems of big systems

This is one of those influential books which may make you start to think about problems in a different way. 

A lot of books about architecture concentrate on simple examples and small-scale problems, and you get the feeling that’s all the authors know about. Many books which do address large systems assume that you are building on a greenfield site, or can somehow ignore the legacies if you are adopting more modern tools for your new systems.

By contrast this is a book about the reality of mixed legacy and new technology environments, written by someone who clearly has real experience of large server farms, big databases, high transaction rates and, perhaps most importantly, important legacy systems with hundreds of thousands of lines of code written in COBOL . 

The book starts by discussing typical problems – things like adding new e-Business presentation layers to existing transactional legacy systems, and briefly summarises how a combination of good architectural practices and appropriate technologies can  address them.

The following chapters present a brief history of large system architectures, including transaction monitors, message queuing and client-server approaches before moving on to object middleware with a discussion on CORBA, Enterprise Java and COM and its relatives. This is followed by a more detailed discussion of how different parts of systems can communicate, and how middleware can be classified. A great strength of the book throughout is that Tony is not obviously partial in the Java vs. Microsoft debate, and instead concentrates on their similarities and on strategies which should be able to work in both cases.

The core of the book starts with a discussion on the different types of "transaction" between a system and its clients (users and other systems), and how these relate to business processes. The following chapters then look at three key issues within this context: resilience; performance and scalability; and security and systems management. In each case there is a clear statement of the problems and objectives, followed by an assessment of the relative merits of various possible architectural solutions.

The final part of the book presents a process which should lead to system architectures better able to meet their non-functional requirements. Tony believes the core of the process is development of a good business process model, which then leads quite directly to an understanding of the system’s components and their interactions. There’s some very good advice on practical implementation approaches, and why process modelling gives better results than
traditional functional analysis.

The final chapters also address key issues such as how to ensure data integrity and accessibility, and how to manage change through integration and designing for flexibility, before revisiting the process issues and summarising how the architecture should develop.

Published in 2000, this pre-dates Microsoft’s .NET initiative, the emergence of vendor-neutral messaging standards and the real advent of web services. Each of these will have a major impact on the sort of systems and issues discussed in this book, and you may therefore also  need to read some material more focused on these technologies and others, but that shouldn’t detract from this book’s value.

Overall this is an excellent book, and I strongly recommend it to anyone trying to understand the nature of large, integrated systems and their architecture.

Buy It From Amazon

Categories: Reviews. Content Types: Book and Software Architecture.

This entry was posted in Reviews. Bookmark the permalink.
Previous Post: A Pattern Approach to Interaction Design
---- Next Post: Software Architecture Bootcamp

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Thoughts on the World Proudly powered by WordPress.

Main Pages

Welcome Page

Architect (Consultancy services)

Developer (Services and Products)

Photographer

Traveller

Writer (Publications and Papers)

Observer (My blog)

Reviewer

Links

Blog Contents

Post Category:

Review Type:

  • Recent Posts

    • When You Wish … A Different Approach To Sourcing
    • The World’s Worst Panorama 2023
    • Rainbows Rising
    • Have I Offended El Gauchito Gil?
    • We’re Going on a Guanaco Hunt!
  • Recent Comments

    • Divitel on It’s Screen Time!
    • Mike Parnell on Camera History
    • ValueBlue on What Do I Mean by "Agile Architecture"?
    • Robert on Combining Risk Factors
    • Paul M Turner on Typically Tropical!
  • Blog Indexes

    Favourite/Major Articles

    All Articles by Category

    All Articles by Title

    Review Index

    Search

    References to www.andrewj.com

    References to www.agilearchitect.org

    Contact Me

    Email me

    @TweetAndrewJ

    Others

    Share

    Facebook

    Google

    Twitter

    Linked In

    Yammer

    Share

    Feeds

    @TweetAndrewJ

    Thoughts on the World (Main Feed)

    Main feed (direct XML)

    Professional Blog

    Photo Blog

    Photo Album

    Review pages

    About my feeds

    © Questa Computing Ltd. 1994 - 2023:
    Questa Computing Ltd. is registered in England and Wales number:2889117.
    Registered office: Coppertrees, Forest Road, Effingham, Leatherhead, KT24 5HE
    Credits, copyright details and cookie policy