When services are integrated
with various business domains, the following introductory questions should be asked:
How can architectures enable transactions across geographic locations? Should these technologies
be centralized? Or should they be dedicated to their geographic boundaries? Business
domains can be positioned in various locations and defined by any geographic boundary the
organization may find appropriate. These decisions are typically driven by the business model
and strategy that a company has established. Clearly, the business-distribution aspect influences
200 Ch. 10 Business Architecture Structural Perspectives
Local
EXHIBIT 10.8 LOCAL INTEGRATION ENVIRONMENT
technological strategies that are crafted to accommodate the driving business objectives. Generally,
there is no service-oriented best practice that dictates how an architecture should be
distributed among geographic areas. The loosely coupled principle, however, supports an architecture
that is more distributed to foster reusability of its components. Consider the following various
geographic location scenarios that are commonly used to describe business and technological
environments.
LOCAL INTEGRATION ENVIRONMENT. An integration effort that is restricted or confined to a
very immediate operating business and technological location, such as a department, or business
unit, is regarded as a geographic local boundary.
Pages:
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361