N1 Grid Architecture Considerations

The SunTone AM cube creates a basis for the definition of the problem space, the architectural activities to decompose that space, and the design and operational efforts to deliver the required solution qualities. In addition, because the framework is not prescriptive, it is easily extended to include new "ilities" associated with N1 Grid systems:

• "How will you address the mobility of the upper layer in the presentation tier?"

• "How will you address the virtualization of the lower layer in the client tier?"

• "How will you address the increased density of multiple upper layers in the data tier?"

In this way, the N1 Grid architecture adds useful questions to the usual SunTone AM discussions, enabling individual consideration of issues such as:

• Treating the data center resources as network-centric elements that operate as a single system to deliver business services

• Extending virtualization beyond one formal "virtual layer" in the stack

• Providing options for the initial provisioning mechanism of each layer

• Simplifying a layer's mobility between containers that can host it

• Expanding the types of relationships between layers

• Automating the checking of dependencies between layers

• Introducing business policy and control to these new N1 Grid solution activities

Architecture frameworks, use cases, and traceable requirements are important components to successful N1 Grid solutions because they enable a thorough definition of the problem space. Part 3 contains detailed examples of these architectural principles. The following sections discuss these principles and frameworks to help you understand where N1 Grid technology makes sense in your environment.