Chapter 5. Resource-Oriented Architectures: Being “In the Web”
Principles and properties | Structures | ||
---|---|---|---|
Versatility | Module | ||
✓ | Conceptual integrity | Dependency | |
Independently changeable | Process | ||
Automatic propagation | ✓ | Data access | |
Buildability | |||
✓ | Growth accommodation | ||
✓ | Entropy resistance |
Architecture is inhabited sculpture.
In this chapter, we will observe that an information-focused architecture in the Enterprise demonstrates some of the same positive properties as the Web: scalability, flexibility, architectural migration strategies, information-driven access control, and so on. In the process, it empowers the business side of the house to make capital investment and software development decisions based on business needs, not simply because fragile technology choices require them to pay for flux.
Introduction
It is with great shame that we as an IT industry must acknowledge this embarrassing fact: it is easier for most organizations to find information on the Web than it is to find information in their own systems. Think about that for a moment. It is easier for them to locate data, through third parties, on a global information system than to do so within environments in which they have complete control and visibility. There are many reasons for this travesty, but the biggest problem is that we tend to use the wrong abstractions internally, overemphasizing our software and services and underemphasizing our data. This wrong-headed approach is a big part of why ...
Get Beautiful Architecture now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.