Buy 2+ books or eBooks, save 55% through December 1. Use code BOOKSGIVING. Shop the sale.
This eBook includes the following formats, accessible from your Account page after purchase:
EPUB The open industry format known for its reflowable content and usability on supported mobile devices.
MOBI The eBook format compatible with the Amazon Kindle and Amazon Kindle applications.
PDF The popular standard, used most often with the free Adobe® Reader® software.
This eBook requires no passwords or activation to read. We customize your eBook by discreetly watermarking it with your name, making it uniquely yours.
Also available in other formats.
Register your product to gain access to bonus material or receive a coupon.
The challenges of designing, building, and maintaining large-scale, distributed enterprise systems are truly daunting. Written by and for IT professionals, IT Architectures and Middleware, Second Edition, will help you rise above the conflicts of new business objectives, new technologies, and vendor wars, allowing you to think clearly and productively about the particular challenges you face.
This book focuses on the essential principles and priorities of system design and emphasizes the new requirements emerging from the rise of e-commerce and distributed, integrated systems. It offers a concise overview of middleware technology alternatives and distributed systems. Numerous increasingly complex examples are incorporated throughout, and the book concludes with some short case studies.
Topics covered include:
In this new edition, with updates throughout, coverage has been expanded to include:
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?
Remote procedure calls.
Remote database access.
Distributed transaction processing.
Message queuing versus distributed transaction processing.
What happened to all this technology?
Using object middleware.
Transactional component middleware.
Final comments on TCM.
Using Web services: A pragmatic approach.
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.
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.
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.
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.
Functions and users.
Inter-relationships and organization.
From silos to distributed environments.
Systems management technology.
Putting it together.
What security is needed.
Traditional distributed system security.
Web services security.
Architecture and security.
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.
What is a process?
Information and processes.
Architecture process patterns.
Clarification and analysis.
The context for integration design.
Recovery and long transactions.
How to do integration design.
What makes a good integration design?
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.
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.
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.