This book introduces a new approach for modeling large enterprise systems: the software fortress model. In the software fortress model, an enterprise architecture is viewed as a series of self-contained, mutually suspicious, marginally cooperating software fortresses interacting with each other through carefully crafted and meticulously managed treaty relationships.
The software fortress model is an intuitive, simple, expressive approach that maps readily to existing technologies such as .NET and Java 2 Enterprise Edition (J2EE). This book is designed to meet an immediate need to define, clarify, and explain the basics of this new modeling methodology for large enterprise software architectures.
Software Fortresses is your essential roadmap to all aspects of software fortresses.
Key topics include:
This book is a must-read for all enterprise software professionals, whether you are a manager seeking to rein in run-away enterprise system complexity, an architect seeking to design interoperable, scalable, and highly secure systems, a consultant expected to give advice on how .NET and J2EE fit into the enterprise space, an implementer wanting to understand how your system relates to a larger enterprise architecture, or a business analyst needing to know that your system requirements will be translated into a successful software implementation.
Click below for Sample Chapter(s) related to this title:
Sample Chapter 7
The Software Fortress Model.
Who Cares about Software Fortresses?
The Goals of This Book.
Who Should Read This Book.
The History of the Software Fortress Model.
The Organization of This Book.
About the Author.
Software Fortress Organization.
The Fortress as a Trust Boundary.
The Main Fortress Types.
The Fortress as a Unit of Interoperability.
Objects, Components, and Fortresses.
Basic Software Fortress Diagram.
Fortress Overview Document.
Treaty Overview Document.
Transactionally Aware Resources.
Tightly Coupled Single-Resource Transactions.
Loosely Coupled Multiple-Resource Transactions.
Tightly Coupled Multiple-Resource Transactions.
The Distributed Transaction Coordinator.
Homogeneous Synchronous Drawbridges.
Heterogeneous Synchronous Drawbridges.
Implementation of Asynchronous Drawbridges.
Persistence and Transactions in Queues.
Heterogeneous Asynchronous Drawbridges.
Homogeneous Asynchronous Drawbridges.
Advantages of Asynchronous Drawbridges
Performance Problems of Asynchronous Drawbridges.
A Treaty between Two Fortresses.
J2EE versus the .NET Approach.
Web Service Fortresses.
J2EE versus the .NET Approach.
Foundation: Components and COMWare.
Transaction Boundary Management.
State Management Revisited.
.NET versus the J2EE Approach.
Broadcast Service Fortresses.
Loosely Coupled Transaction Management Service Fortresses.
Treaty Management Fortresses.
Group One: Enterprise Overview Questions.
Question 1: Do we need a software fortress architecture?
Question 2: Do we all have the same understanding of the software fortress methodology?
Question 3: Have the requirements for each fortress been clearly articulated?
Question 4: Have our fortresses been partitioned with organizational boundaries in mind?
Question 5: Are our fortresses organized around natural trust boundaries?
Question 6: Have we really made enterprise-level decisions at the enterprise level and fortress-level decisions at the fortress level?
Question 7: Have we confused objects, components, and fortresses?
Question 8: Have we identified all of the security issues?
Group Two: Enterprise Architecture Questions.
Question 9: Do we have the right number of fortresses?
Question 10: Are all drawbridge requests idempotent?
Question 11: Are all drawbridge requests for substantial work?
Question 12: Do we have any tightly coupled transactions across fortresses?
Question 13: Are all drawbridges heterogeneous asynchronous?
Question 14: Does all interfortress communication pass through drawbridges?
Question 15: Have we considered all of the risk factors inherent in our presentation and Web service fortresses?
Group Three: Fortress Architecture Questions.
Question 16: Are we considering fortress-appropriate technologies?
Question 17: If we must use a synchronous drawbridge, do we have an asynchronous back end?
Question 18: Are we using more than one technology base within a single fortress?
Question 19: Have we designed a scale-out architecture?
Question 20: Have we designed a fortress architecture that can leverage loosely coupled clusters for reliability?
Question 21: Have we designed adequate security for each of our guards?
Question 22: Have we built effective walls around the fortress?
Question 23: Are we using only homogeneous synchronous communications within the fortress?
Question 24: Do all of our outgoing communications pass through envoys?
Question 25: Is all of our data being stored in the data strongbox?
The ProcessOrder Drawbridges.
The CheckInventory Drawbridges.
Ten Important Points about Software Fortresses.
Ten Reasons to Adopt the Software Fortress Model.
Ten Rules for Software Fortress Design.
Ten Controversial Ideas within the Software Fortress Model.
Ten Considerations for Evaluating J2EE versus .NET.
Ten Observations on the State of the Software Industry.
Where to Go Next.
You and I have never met. I have no idea what your business is. However, I do know what your enterprise architecture looks like. I can even show you the exact picture you use to describe your enterprise system. Take a look at Figure 0.1. Look familiar?
It goes without saying that your enterprise is a perfect three-tier/N-tier software architecture. When describing your system, you wax poetic about your perky presentation tier, accepting HTTP requests from complacent clients and SOAP requests from congenial collaborators. You illuminate in minutiae how you manage your middle tier, running well behaved business logic cherubs, all gleefully sharing database connections and other valuable system resources. Behind all of this, your enterprise-wide database shouts encouragement from its sheltered back-end.
See? I told you I know what your enterprise architecture looks like. I also know one other thing. I know you lie. You lie through your teeth.Your enterprise architecture looks nothing like Figure 0.1. Do you want to see the real picture of your enterprise architecture? Take a look at Figure 0.2. But first, sit down. It isn't pretty!
In the real world, your clients are not meek, but malicious. Your middle tier is not well behaved, but made up of a disparate bunch of applications developed without regard for the needs of their stable mates. Your "database" is not an enterprise-wide anything but rather a series of disorganized data storage technologies that spend most of their time cringing from the unreasonable and often conflicting demands of the business logic.
As architects, we have two choices. We can ignore this chaos or we can model it. When we model it, we have the opportunity to bring it under some degree of intellectual control.
This book introduces a new approach for modeling large enterprise systems. This approach is called the software fortress modeltm. The software fortress model treats enterprise systems as a series of self contained software fortresses. Each fortress makes its own choices as to software platform and data storage mechanisms and interacts with other fortresses through carefully crafted treaties. Without going into too much detail this early, a view of the same enterprise as shown in Figure 0.2, as seen from the software fortress model, looks like Figure 0.3. Don't worry at this point about what the cartoon figures mean, they will become familiar soon enough.
The software fortress model pushes the simplification of the enterprise further and further. As we use the model to decompose the enterprise, Figure 0.3 becomes a series of collaborations, as shown in Figure 0.4.
I will discuss what the software fortress model is throughout this book. For now, let's focus on why we need this model.
The most important reason we need the software fortress model is to better understand how our systems interact within our overall enterprise architecture. Even without knowing the details of how the software fortress model works, you can quickly get the sense that Figures 0.3 and 0.4 are a lot more approachable than Figure 0.2.
We already have many good techniques for modeling software systems. The most prevalent is the Universal Modeling Language (UML). However existing systems, including UML, focus on the issues involved with designing software systems. They have little to offer the enterprise architect in modeling how the various software systems that make up the enterprise architecture relate to each other. In other words, they are fine for modeling a sales system, an inventory system, or an accounts payable system. They are not useful in showing how a sales, inventory, and accounts payable system need to work together to coordinate a customer purchase.
The software fortress model picks up where techniques like UML leave off. Or, to be more precise, UML picks up where the software fortress model leaves off. The software fortress model helps us describe and plan for the relationships between software systems. It is these relationships that ultimately define the enterprise architecture. UML and related technologies can then be used to document how those individual software systems are designed.
The software fortress model has a lot to offer, especially for the high level manager, who is trying to understand the overall enterprise architecture, and for the enterprise architect, who is trying to explain it.
For CTO types, the software fortress model offers these immediate payoffs:
But it is not just CTOs and enterprise architects that will gain from the software fortress model, this model has the power to transform our entire industry. For the first time, our entire industry will share one lingua franca for discussing enterprise applications. Customers and clients will be able to readily communicate with programmers and architects; Java programmers will be able understand VisualBasic programmers; and architects from different business fields will be able to compare approaches to common problems.
Over time, the software fortress model will influence the software platforms themselves. Tools will appear to directly support the model. Platforms will evolve as the model exposes underlying platform weaknesses. New technological approaches will be explored as the model helps us better understand the needs of the enterprise.
Perhaps the most important contribution of the model is simplification. Simplification of security, simplification of interoperability, and simplification of collaboration. Simple systems are inherently better than complex systems. They are cheaper to build, they are more reliable, and they are more secure. We can all get behind that.
The software fortress model is still quite young, even by software standards. However I have already presented the main ideas that make up this model in person to over three thousand developers and conducted in-depth workshops with very high level enterprise architects from more than a dozen large companies. I have also introduced the ideas to the readership of the ObjectWatch Newsletter, which includes more than 20,000 readers including highly placed managers and architects at virtually all of the Fortune 500 companies.
The response to the software fortress model, even in its relative state of immaturity, has been overwhelming. Almost everybody who is exposed to the software fortress model feels a strong sense of resonance, as if this model addresses a very basic requirement at their organization: the requirement to model and simplify their enterprise's complexity.
This book is designed to meet an
Click below to download the Index file related to this title: