* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Download Presentation - Galiel 3.14 Ltd.
Commitment ordering wikipedia , lookup
Global serializability wikipedia , lookup
Expense and cost recovery system (ECRS) wikipedia , lookup
Serializability wikipedia , lookup
Oracle Database wikipedia , lookup
Relational model wikipedia , lookup
Concurrency control wikipedia , lookup
Database model wikipedia , lookup
LiveDist: Real-Time Distribution of Databases, with High-Volume of Updates Dynamic and selective distribution of a central or distributed database, to a large number of clients, in a changing topology. Galiel-3.14 Ltd. has intellectual property rights relating to implementations of the technology described in this presentation. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form, or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written consent of the publisher. This presentation is provided “AS IS” without warranty of any kind, either express of implied, including, but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. This presentation could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. These changes will be incorporated in new editions of the presentation. Galiel-3.14 Ltd’ May make improvements and/or change in any technology, product, or program described in this presentation at any time. High Volume of Updates and Large Number of Clients Supports the distribution of thousands of SQL database operations per second . Each client defines a filter, and only database operations on entities which are selected by the filter, are sent to the client. LiveDist can selectively distribute the information to many thousands of clients, with no degradation in performance. Each client can change his filter as required . For additional information please vist our site: http://www.galiel314.com or http://www.livedist.com Clients can be: Browsers (thin clients) Applications, running on desktops or laptops Cellular phones Database server machines External software systems Any HTTP client Distributed Databases LiveDist supports the distribution of a database among many sites. There is no master site. Each site defines filters for the entities it receives from each connected site. A site can change its filters as required. All failures are automatically recovered. LiveDist supports fast synchronization between sites, which have been disconnected for a long time. LiveDist supports fast synchronization between sites, following topology changes. Advanced Features LiveDist distributes hierarchical objects (mapped to relational database), instead of just plain table rows. LiveDist supports changes of database structure on the fly (there is no need to stop the system following a change in the database structure). LiveDist requires no administration. Proven Technology Used in large and critical systems, developed by the Israeli Air Force and two major Israeli defense conglomerates. Platforms The Java version of LiveDist currently supports Oracle database engine. The C# version of LiveDist supports SQL-Server and Oracle. Advantages over Database Replication Clients of LiveDist are not required to be databases. A client can display distributed data, as dynamically refreshed graphical symbols, or as dynamically refreshed tables in a browser, etc. Database replication cannot handle a large number of clients, while LiveDist can scale to support a practically unlimited number of clients Database replication requires sophisticated administration, while LiveDist requires none. Database replication systems require expensive hardware, while LiveDist runs on low-cost machines. Database replication performs poorly when new database nodes are added and when filters are changed. Advantages over Messaging Systems with Persistent Queues (Store & Forward) Messaging systems cannot automatically handle topology changes (especially when new clients join the network). Messaging systems cannot automatically handle dynamic filter changes by the working clients. In a messaging system, a persistent queue is defined for each client (on a disk), causing linear performance degradation when the number of clients is increased. Messaging systems require complicated administration.