This transformational architectural concept not only
describes conversion requirements for data and protocols but also advocates policies and standards
that enable flawless interaction and collaboration between technological constituents.
Imagine, for example, a consumer and a service, each of which is empowered by its
dedicated platform running on different operating systems and supporting incompatible message
formats. Can this communication scenario operate properly without appropriate protocol and data
translation? How can such an operation be translated between these remote assets? How would
security be maintained in such an interoperable environment? Hence, the transformation machine
concept describes vital solutions to incompatibility problems that typically emerge in a distributed
and federated technological environment. The more scattered and globally dispersed a business,
the more vital data, protocol, and operation transformations are to the technological environment.
Exhibit 15.16 illustrates the three major responsibilities of a transformation architectural concept.
Rendering Machine. Customer-facing software applications heavily rely on presentation layers
to provide adequate and efficient user-interface capabilities. The conceptual rendering machine
describes presentation layer solutions that enable users to communicate with backend services.
Content rendering is typically accomplished on the client side.
Pages:
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563