Architecture for Distributed ERP Systems

Abstract

AbstractIn a distributed ERP (Enterprise Resource Planning) system, the different local ERP systems are integrated in such a way that each local system can use the resources/stocks managed by the other local ERP systems. Businesses with branch offices may derive great benefits from such systems. In theory, such a system can be built by using a distributed DBMS (Data Base Management System). However, distributed DBMSs are not used in practice as e.g. performance and local autonomy are low. In distributed databases with relaxed ACID properties (Atomicity, Consistency, Isolation, and Durability), it is possible to optimize performance, local autonomy, and availability by using short duration locking. In such systems, data is not locked across locations, i.e. data is not locked across a dialog with a user, and replicated data must be updated asynchronously. In this paper, we will describe how it is possible to design a distributed ERP system by using databases with relaxed ACID properties. The techniques described are general in the sense that most package software run on separate computers may be integrated by using the same methods. The author has cooperated with one of the major ERP software companies in analyzing how the company can design such a distributed version of their ERP system.KeywordsPrimary CopyTransaction ModelLocal AutonomySite FailureBranch OfficeThese keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.