Making the supply decisions
Supply decisions can be made once you have defined your units of functionality then identified and allocated these to an architectural layer.[2] These decisions consider whether each functional unit should be a component or a web service and whether they can be reused/rented/bought/built (R/R/B/B). For most applications, the considerations in Table 3.2 hold true.
[2] Briefly, these architectural layers consist of:
low-level infrastructure, including the hardware, operating systems, and virtual platforms such as Enterprise Java and .NET;
web services applied as part of the technical infrastructure; examples include authentication, long-running transactions, and management;
web services applied at the business level; examples ...
Get Service- and Component-based Development: Using Select Perspective™ and UML 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.
