Figures. Boxes. Preface. Acknowledgments. 1. The Problem.
Example: Moving to e-business.
What is IT architecture?
Why is this different from what we did before?
Rewrite or evolve?
Who develops the architecture?
Summary. 2. The Emergence of Standard Middleware.
Remote procedure calls.
Remote database access.
Distributed transaction processing.
Message queuing versus distributed transaction processing.
What happened to all this technology?
Summary. 3. Objects, Components, and the Web.
Using object middleware.
Transactional component middleware.
Final comments on TCM.
Summary. 4. Web Services.
Using Web services: A pragmatic approach.
Summary. 5. A Technical Summary of Middleware.
The communications link.
The middleware protocol.
The programmatic interface.
Naming and directory services.
Comments on Web services.
Vendor platform architectures.
Using vendor architectures.
Strawman for user target architecture.
Summary. 6. Using Middleware to Build Distributed Applications.
What is middleware for?
Support for business processes.
The presentation tier.
The processing tier.
The data tier.
Services versus tiers.
Middleware bus architectures.
Web services architectures.
Loosely coupled versus tightly coupled.
Summary. 7. Resiliency.
Using backup servers.
Cleanup work in progress.
Activating the application.
Reprocessing "lost" messages.
Applying resiliency techniques.
System software failure.
Application software failure.
Developing a resiliency strategy.
Summary. 8. Performance and Scalability.
The un-slippery slope.
Transactional component containers.
Using remote database access for real-time transactions.
Conclusions about real time.
Is distribution an alternative?
Business intelligence systems.
Ad hoc database queries.
Backups and recovery.
Design for scalability and performance.
Summary. 9. Systems Management.
Functions and users.
Inter-relationships and organization.
From silos to distributed environments.
Systems management technology.
Putting it together.
Summary. 10. Security.
What security is needed.
Traditional distributed system security.
Web services security.
Architecture and security.
Summary. 11. Application Design and IT Architecture.
Problems with today's design approaches.
Design up front or as needed?
The role of business rules.
Silo and monolithic development.
The role of architecture.
Levels of design.
Reconciling design approaches.
Summary. 12. Implementing Business Processes.
What is a process?
Information and processes.
Architecture process patterns.
Clarification and analysis.
Summary. 13. Integration Design.
The context for integration design.
Recovery and long transactions.
How to do integration design.
What makes a good integration design?
Summary. 14. Information Access and Information Accuracy.
Basic process information.
Marketing and strategic business analysis.
Summary of requirements for information access.
Shared data or controlled duplication.
Creating consistency in existing databases.
The technical problem.
The data migration problem.
The business process problem.
The information controller.
Summary. 15. Changing and Integrating Applications.
Creating a presentation layer.
Interface size mismatch.
Turning existing applications into services.
Building a middle tier.
Business processing change with new interfaces.
Changing the middleware between transaction servers.
Summary. 16. Building an IT Architecture.
Case 1: Providing an integration infrastructure.
Case 2: Creating a service-oriented architecture.
Case 3: Developing a new application.
Remarks on common mistakes.
What does the future hold?
The key points to remember.
Middleware technology alternatives.
IT architecture guidelines.
Distributed systems technology principles.
Distributed systems implementation design. Appendix: Acronyms. Index.