Cyprus Villas Banner 1

kBOS Applied Knowledge Engineering Methodologyknowledge management

kBOS Applied Knowledge Engineering Methodology

kBOS Introductionknowledge management
kBOS Technology Innovationsknowledge management
kBOS history of developmentknowledge management
kBOS Strategic Knowledge Managementknowledge management
kBOS Process Optimisationknowledge management
Multilevel Enterprise Integrationknowledge management
Advanced Business Intelligenceknowledge management
The kBOS Platform Software Characteristicsknowledge management
kBOS Workflowknowledge management
kBOS Content Managementknowledge management
kBOS Web Services Middlewareknowledge management
kBOS Datawarehousingknowledge management
kBOS Unified Solutionsknowledge management
kBOS Sector Solutionsknowledge management
kBOS Financial Sector Softwareknowledge management
kBOS Health care softwareknowledge management
kBOS Shipping softwareknowledge management
Applicationsknowledge management
Contact Usknowledge management

11/25/2015 2:05:57 AM
Visitors : 756805

Integration hub and spoke architectures

Current integration solutions are based, in the main, on centralised “hub-and-spoke” architectures that grew out of intra-enterprise application integration and are ill suited to meet the demands of what is fundamentally a distributed problem. Centralised architectures applied to decentralised business relationships result in a loss of efficiency and increased costs for companies since the initial design of these centralised architectures do take into consideration the different aspects of decentralised architectures. Web services promise a potential solution, but the standards and solutions being developed do not provide the necessary process integration capabilities.

The answer to this problem is a viable, fully distributed, network-based integration architecture, known as peer-to-peer which can help meet these new cross-enterprise challenges.

The essential element of any distributed system is to enable the participants to maintain autonomy and control. This greatly simplifies development and ongoing change management, resulting in dramatically lower implementation costs, deployment time and the ongoing cost of maintaining the network. A major disadvantage in the centralised “hub-and-spoke” model is that it requires a top-down development methodology for what has always been a bottom-up problem.

The cross-enterprise integration problem can be defined as "bottom-up" because applications that are to be integrated across a distributed network are already pre-existing software in their own right. To operate at maximum profitability, application owners need to keep specific control over their applications and the way in which they are accessed. That is to be able to change or replace an application without impacting the entire integration solution is important to the stability and effectiveness of the network.

     Copyright © 2015  INLECOM & K-NET

Developed by eBOS Technologies Ltd