This chapter is intended as an introduction for specialists who have not yet dealt with the subject of integration.Ĭhapter 2, Base Technologies, describes a selection of base technologies. This idea is reflected in the structure of the book.Ĭhapter 1, Basic Principles, covers the fundamental integration concepts. It allows any type of integration problem to be represented, including traditional ETL (Extract, Transform, and Load), classic EAI (Enterprise Application Integration), EDA (event-driven architecture), and grid computing. This kind of layering is not common in technical literature, but it has been proven to be very useful in practice. For this reason, the Trivadis Integration Architecture Blueprint subdivides the integration layer into further layers. In this case, this means structuring it in such a way that standardized, tried-and-tested basic components can be combined to form a functioning whole, with the help of tools and products. The basic issue involves, on the one hand, deciding how to divide an integration solution into individual areas so that it meets the customer requirements, and on the other hand, how it can be implemented with a reasonable amount of effort. What This Book Coversĭespite the wide variety of useful and comprehensive books and other publications on the subject of integration, the approaches that they describe often lack practical relevance. The blueprint makes it possible to implement application systems correctly without losing sight of the bigger picture: a high performance, flexible, scalable, and affordable enterprise architecture. The process of developing new systems is significantly simplified by dividing the integration architecture into process, mediation, collection and distribution, and communication layers. The Trivadis Integration Architecture Blueprint shows how to structure, describe, and understand existing application landscapes from the perspective of integration. It creates transparency in the confused world of product developers and theoretical concepts. It achieves this by representing common integration approaches, such as Enterprise Application Integration (EAI) Extract, Transform, and Load (ETL) event-driven architecture (EDA) and others, in a clearly and simply structured blueprint. The Trivadis Integration Architecture Blueprint indicates how integration architectures can be implemented in practice. For this reason, it is essential to transform the abstract concept of integration into concrete, clearly structured, and practical implementation variants. Smart integration mechanisms are needed to allow existing systems, as well as the functionality provided by individual applications, to be brought together into a new fully functioning whole. In addition, SOA is finally offering mechanisms that put the focus on existing systems, and make it possible to continue to use them. Because of SOA, functions provided by individual systems are now available in a single standardized form throughout organizations, and even outside their corporate boundaries. SOA represents an end-to-end approach to the IT system landscape as the support function for business processes. Nearly all organizations and vendors are designing or implementing applications with SOA capability. Furthermore, SOA is becoming more and more widely accepted as a standard architecture. It is increasingly rare to find applications developed for a specific purpose that do not need to exchange information with other systems. The era of isolated business information systems-so-called silos or stove-pipe architectures-is finally over. With the widespread use of service-oriented architecture (SOA), the integration of different IT systems has gained a new relevance. Service-Oriented Architecture- An Integration Blueprint
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |