DOCSLIB.ORG

A Centralized Ledger Database for Universal Audit and Verification

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
A Centralized Ledger Database for Universal Audit and Verification LedgerDB: A Centralized Ledger Database for Universal Audit and Verification Xinying Yangy, Yuan Zhangy, Sheng Wangx, Benquan Yuy, Feifei Lix, Yize Liy, Wenyuan Yany yAnt Financial Services Group xAlibaba Group fxinying.yang,yuenzhang.zy,sh.wang,benquan.ybq,lifeifei,yize.lyz,[email protected] ABSTRACT certain consensus protocol (e.g., PoW [32], PBFT [14], Hon- The emergence of Blockchain has attracted widespread at- eyBadgerBFT [28]). Decentralization is a fundamental basis tention. However, we observe that in practice, many ap- for blockchain systems, including both permissionless (e.g., plications on permissioned blockchains do not benefit from Bitcoin, Ethereum [21]) and permissioned (e.g., Hyperledger the decentralized architecture. When decentralized architec- Fabric [6], Corda [11], Quorum [31]) systems. ture is used but not required, system performance is often A permissionless blockchain usually offers its cryptocur- restricted, resulting in low throughput, high latency, and rency to incentivize participants, which benefits from the significant storage overhead. Hence, we propose LedgerDB decentralized ecosystem. However, in permissioned block- on Alibaba Cloud, which is a centralized ledger database chains, it has not been shown that the decentralized archi- with tamper-evidence and non-repudiation features similar tecture is indispensable, although they have been adopted to blockchain, and provides strong auditability. LedgerDB in many scenarios (such as IP protection, supply chain, and has much higher throughput compared to blockchains. It merchandise provenance). Interestingly, many applications offers stronger auditability by adopting a TSA two-way peg deploy all their blockchain nodes on a BaaS (Blockchain- protocol, which prevents malicious behaviors from both users as-a-Service) environment maintained by a single service and service providers. LedgerDB supports verifiable data provider (e.g., Microsoft Azure [8] and Alibaba Cloud [4]). removals demanded by many real-world applications, which This instead leads to a centralized infrastructure. As there are able to remove obsolete records for storage saving and is still no widespread of truly decentralized deployments in hide records for regulatory purpose, without compromis- permissioned blockchain use cases, many advocates are veer- ing its verifiability. Experimental evaluation shows that ing back to re-examine the necessity of its decentralization. LedgerDB's throughput is 80× higher than state-of-the-art Gartner predicts that at least 20% of projects envisioned to permissioned blockchain (i.e., Hyperledger Fabric). Many run on permissioned blockchains will instead run on central- blockchain customers (e.g., IP protection and supply chain) ized auditable ledgers by 2021 [23]. on Alibaba Cloud have switched to LedgerDB for its high To reform decentralization in permissioned blockchains, throughput, low latency, strong auditability, and ease of use. we propose LedgerDB { a ledger database that provides tamper-evidence and non-repudiation features in a central- PVLDB Reference Format: ized manner, which realizes both strong auditability and Xinying Yang, Yuan Zhang, Sheng Wang, Benquan Yu, Feifei Li, high performance. We call it a centralized ledger database Yize Li, and Wenyuan Yan. LedgerDB: A Centralized Ledger (CLD) system, which pertains to centralized ledger technol- Database for Universal Audit and Verification. PVLDB, 13(12): ogy (CLT) that is opposed to decentralized ledger technology 3138-3151, 2020. DOI: https://doi.org/10.14778/3415478.3415540 (DLT) in blockchain. LedgerDB is developed and widely adopted at Ant Financial from Alibaba Group. Its major designs are inspired by limitations in conventional permis- 1. INTRODUCTION sioned blockchains [6, 26, 11, 31, 18, 29, 30] and ledger Since the launch of Bitcoin [32], blockchain has been in- databases [7, 40]. troduced to many applications as a new data collaboration First, we observe that many use cases of permissioned paradigm. It enables applications to be operated by mu- blockchains (e.g., provenance and notarization) only seek for tually distrusting participants. A blockchain system im- the tamper resistance from cryptography-protected struc- plements hash-entangled data blocks to provide a tamper- tures, such as hashed chains and Merkle trees [27]. Often- evident ledger with bulks of transactions committed by a times, none of the other features (e.g., decentralization and smart contract) are utilized. In this case, a simplified au- ditable ledger service from a credible central authority with This work is licensed under the Creative Commons Attribution- essential data manipulation support is sufficient. It tends NonCommercial-NoDerivatives 4.0 International License. To view a copy to be more appealing against blockchains, due to its high of this license, visit http://creativecommons.org/licenses/by-nc-nd/4.0/. For throughput, low latency, and ease of use. any use beyond those covered by this license, obtain permission by emailing Second, the threat model of permissioned blockchain is [email protected]. Copyright is held by the owner/author(s). Publication rights inadequate for real-world audit. For external (i.e., third- licensed to the VLDB Endowment. party) auditors beyond its consortium, data replication guar- Proceedings of the VLDB Endowment, Vol. 13, No. 12 ISSN 2150-8097. ded by consensus protocols seems deceptive. For example, DOI: https://doi.org/10.14778/3415478.3415540 3138 Table 1: Key comparisons between LedgerDB and other systems. Throughput Auditability Removal Non-Repudiation Provenance System (max TPS) external third party peg capability purge occult server-side client-side native clue LedgerDB 100K+ 3 TSA 3 strong 3 3 3 3 3 QLDB [7] 1K+ 7 7 7 weak 7 7 7 7 7 Hyperledger [6] 1K+ 7 7 7 weak 7 7 3 3 7 ProvenDB [40] 10K+ 7 Bitcoin 3 medium 7 3 7 7 7 Factom [43] 10+ 3 Bitcoin 3 strong 7 7 3 3 7 with the endorsement from all peers, they are able to fabri- strong auditability, broad verification coverage, low stor- cate fake evidence (e.g., modify a transaction from ledger) age cost, as well as high throughput. against external auditors without being noticed. What is • To ensure strong auditability, we adopt non-repudiable worse, the partial endorsement from a majority is already signings and a TSA peg protocol to prevent malicious be- sufficient to conduct above deception, if others fail to provide haviors (defined in § 2.2) from users and LSP. original chain proofs to external auditor. As a consequence, • We provide verifiable data removal operators to resolve permissioned blockchains only retain limited auditability. storage overhead and regulatory issues. They help remove Third, though some centralized auditable ledger databases obsolete records (purge) or hide record content (occult) emerge as alternatives to permissoned blockchains, they how- without compromising verifiability. We also provide na- ever excessively assume a trustful service provider. For ex- tive primitives (clue) to facilitate the tracking of applicati- ample, AWS discloses QLDB [7, 13] that leverages an im- on-level data provenance. mutable and verifiable ledger; Oracle announces its blockcha- • To sustain high throughput for write-intensive scenarios, in table [35]. These auditable ledgers require that the ledger we enhance LedgerDB with tailored components, such as service provider (LSP) is fully trusted, such that historical an execute-commit-index transaction workflow, a batch records can be archived and verified at the server side. It re- accumulated Merkle-tree (bAMT ), and a clue index (cSL). mains unknown whether the returned records are tampered Our experimental result shows that LedgerDB achieves by LSP, especially when it colludes with a certain user. excellent throughput (i.e., 300,000 TPS), which is 80× Fourth, the immutability1 provided by existing systems and 30× higher than Hyperledger Fabric and QLDB re- implies that each piece of committed data is permanently spectively. disclosed on the ledger as the tamper evidence, which indeed The rest of this paper is organized as follows. We discuss causes prohibitive storage overhead and regulatory issues in limitations in current solutions and our design goals in § 2. real-world applications. Many blockchain users wish to clean We overview LedgerDB in § 3, and then present our detailed up obsolete records for storage savings, since it will other- designs (i.e., journal management, verification mechanism, wise become unaffordable as data volume grows. In terms and provenance support) in § 4, § 5 and § 6 respectively. of regulatory issues, those records violating law or morality Use cases and real-world practices are provided in § 7. We (e.g., upload someone's residential address without prior ap- provide experimental evaluation in § 8 and related work in proval) cannot be erased once it has been committed, which § 9, before we conclude in § 10. is undesirable in many applications. To address these issues, LedgerDB adopts a centralized ar- chitecture and a stateless journal storage model, rather than 2. PRELIMINARIES AND DESIGN GOALS tightly-coupled transaction state model in most blockchain We work on the design of a ledger database that supports systems [21, 30], to achieve high system throughput. It blockchain-like (especially permissioned blockchain) applica- adopts multi-granularity verification and non-repudiation pr- tions using a centralized architecture. It records immutable otocols, which prevents malicious behaviors from (colluded) application transactions
Load more

Recommended publications
  • General Ledger Budgeting User Guide
    General Ledger Budgeting User Guide Version 9.0 February 2006 Document Number FBUG-90UW-01 Lawson Enterprise Financial Management Legal Notices Lawson® does not warrant the content of this document or the results of its use. Lawson may change this document without notice. Export Notice: Pursuant to your agreement with Lawson, you are required (at your own expense) to comply with all laws, rules, regulations, and lawful orders of any governmental body that apply to you and the products, services or information provided to you by Lawson. This obligation includes, without limitation, compliance with the U.S. Foreign Corrupt Practices Act (which prohibits certain payments to governmental ofÞcials and political parties), U.S. export control regulations, and U.S. regulations of international boycotts. Without limiting the foregoing, you may not use, distribute or export the products, services or information provided to you by Lawson except as permitted by your agreement with Lawson and any applicable laws, rules, regulations or orders. Non-compliance with any such law, rule, regulation or order shall constitute a material breach of your agreement with Lawson. Trademark and Copyright Notices: All brand or product names mentioned herein are trademarks or registered trademarks of Lawson, or the respective trademark owners. Lawson customers or authorized Lawson business partners may copy or transmit this document for their internal use only. Any other use or transmission requires advance written approval of Lawson. © Copyright 2006 Lawson Software, Inc. All rights reserved. Contents List of Figures 7 Chapter 1 Overview of Budgeting 9 Budgeting ProcessFlow...............................................................9 HowBudgeting Integrates WithOtherLawsonApplications..................... 11 What is a Budget?...................................................................
    [Show full text]
  • A73 Cash Basis Accounting
    World A73 Cash Basis Accounting Net Change with new Cash Basis Accounting program: The following table lists the enhancements that have been made to the Cash Basis Accounting program as of A7.3 cum 15 and A8.1 cum 6. CHANGE EXPLANATION AND BENEFIT Batch Type Previously cash basis batches were assigned a batch type of ‘G’. Now cash basis batches have a batch type of ‘CB’, making it easier to distinguish cash basis batches from general ledger batches. Batch Creation Previously, if creating cash basis entries for all eligible transactions, all cash basis entries would be created in one batch. Now cash basis entries will be in separate batches based on a one-to-one batch ratio with the originating AA ledger batch. For example, if cash basis entries were created from 5 separate AA ledger batches, there will be 5 resulting AZ ledger batches. This will make it simpler to track posting issues as well as alleviate problems inquiring on cash basis entries where there were potential duplicate document numbers/types within the same batch. Batch Number Previously cash basis batch numbers were unique in relation to the AA ledger batch that corresponded to the cash basis entries. Now the cash basis batch number will match the original AA ledger batch, making it easier to track and audit cash basis entries in relation to the originating transactions. Credit Note Prior to A7.3 cum 14/A8.1 cum 4, the option to assign a document type Reimbursement other than PA to the voucher generated for reimbursement did not exist.
    [Show full text]
  • A Logical Framework for Temporal Deductive Databases S
    A logical framework for temporal deductive databases S. M. Sripada Departmentof Computing Imperial College of Science& Technology 180 Queen’sGate, London SW7 2BZ Abstract researchers have incorporated time into conventional databasesusing various schemes Temporal deductive databases are deductive providing different capabilities for handling databaseswith an ability to representboth valid temporal information. In particular, work has time and transaction time. The work is basedon been done on adding temporal information to the Event Calculus of Kowalski & Sergot. Event conventionaldatabases to turn them into temporal Calculus is a treatment of time, based on the databases. However, no work is done on notion of events, in first-order classical logic handling both transaction time and valid time in augmentedwith negation as failure. It formalizes deductive databases.In this paper we propose a the semanticsof valid time in deductivedatabases framework for dealing with time in temporal and offers capability for the semantic validation deductivedatabases. of updates and default reasoning. In this paper, the Event Calculus is extended to include the Snodgrass dz Ahn [16,17] describe a concept of transaction time. The resulting classification of databasesdepending on their framework is capable of handling both proactive ability to represent temporal information. They and retroactive updates symmetrically. Error identify three different concepts of time - valid correction is achievedwithout deletionsby means time, transaction time and user-defined time. Of of negation as failure. The semantics of these, user-defined time is temporal transaction time is formalised and the axioms of information of some kind that is of interest to the the Event Calculus are modified to cater for user but does not concern a DBMS.
    [Show full text]
  • Using Blockchain Technology to Secure the Internet of Things
    Using Blockchain Technology to Secure the Internet of Things Presented by the Blockchain/ Distributed Ledger Working Group © 2018 Cloud Security Alliance – All Rights Reserved. You may download, store, display on your computer, view, print, and link to Using Blockchain Technology to Secure the Internet of Things subject to the following: (a) the Document may be used solely for your personal, informational, non- commercial use; (b) the Report may not be modified or altered in any way; (c) the Document may not be redistributed; and (d) the trademark, copyright or other notices may not be removed. You may quote portions of the Document as permitted by the Fair Use provisions of the United States Copyright Act, provided that you attribute the portions to the Using Blockchain Technology to Secure the Internet of Things paper. Blockchain/Distributed Ledger Technology Working Group | Using Blockchain Technology to Secure the Internet of Things 2 © Copyright 2018, Cloud Security Alliance. All rights reserved. ABOUT CSA The Cloud Security Alliance is a not-for-profit organization with a mission to promote the use of best practices for providing security assurance within Cloud Computing, and to provide education on the uses of Cloud Computing to help secure all other forms of computing. The Cloud Security Alliance is led by a broad coalition of industry practitioners, corporations, associations and other key stakeholders. For further information, visit us at www.cloudsecurityalliance.org and follow us on Twitter @cloudsa. Blockchain/Distributed Ledger Technology Working Group | Using Blockchain Technology to Secure the Internet of Things 3 © Copyright 2018, Cloud Security Alliance. All rights reserved.
    [Show full text]
  • Oracle General Ledger
    ORACLE DATA SHEET ORACLE GENERAL LEDGER KEY FEATURES Oracle® General Ledger is a comprehensive financial management • Flexible chart of accounts and reporting structures solution that provides highly automated financial processing, • Centralized setup for fast effective management control, and real-time visibility to financial implementations • Simultaneous accounting for results. It provides everything you need to meet financial multiple reporting requirements compliance and improve your bottom line. Oracle General Ledger • Compliance with multiple is part of the Oracle E-Business Suite, an integrated suite of legislative, industry or geographic requirements applications that drive enterprise profitability, reduce costs, • Spreadsheet integration for improve internal controls and increase efficiency. journals, budgets, reporting, and currency rates • Tight internal controls and Capitalize on Global Opportunities access to legal entity and ledger data Meet Varied Reporting Standards with a Flexible Accounting Model • Multi-ledger financial reporting for real-time, In today’s complex, global, and regulated environment, finance organizations face enterprise-wide visibility challenges in trying to comply with local regulations and multiple reporting • Robust drilldowns to underlying transactions requirements. Oracle General Ledger allows companies to meet these challenges in • Professional quality reporting a very streamlined and automated fashion. Multiple ledgers can be assigned to a • One-touch multi-ledger legal entity to meet statutory, corporate, regulatory, and management reporting. All processing accounting representations can be simultaneously maintained for a single • Automated month-end close processing transaction. For example, a single journal entered in the main, record-keeping • Fastest and most scalable ledger can be automatically represented in multiple ledgers even if each ledger uses general ledger on the market a different chart of accounts, calendar, currency, and accounting principle.
    [Show full text]
  • Temporal Metadata for Discovery
    Temporal Metadata for Discovery A review of current practice Makx Dekkers AMI Consult SARL Massimo Craglia (Editor) European Commission DG JRC Institute for Environment and Sustainability EUR 23209 EN - 2008 The mission of the Institute for Environment and Sustainability is to provide scientific-technical support to the European Union’s Policies for the protection and sustainable development of the European and global environment. European Commission Joint Research Centre Institute for Environment and Sustainability Contact information Makx Dekkers Address: AMI Consult Société à responsabilité limitée B.P. 647 2016 Luxembourg E-mail: [email protected] Massimo Craglia (Editor) Address: European Commission Joint Research Centre Institute for Environment and Sustainability Spatial Data Infrastructures Unit TP262, Via Fermi 2749 I-21027 Ispra (VA) ITALY E-mail: [email protected] Tel.: +39-0332-786269 Fax: +39-0332-786325 http://ies.jrc.ec.europa.eu/ http://www.jrc.ec.europa.eu/ Legal Notice Neither the European Commission nor any person acting on behalf of the Commission is responsible for the use which might be made of this publication. Europe Direct is a service to help you find answers to your questions about the European Union Freephone number (*): 00 800 6 7 8 9 10 11 (*) Certain mobile telephone operators do not allow access to 00 800 numbers or these calls may be billed. A great deal of additional information on the European Union is available on the Internet. It can be accessed through the Europa server http://europa.eu/ JRC 42620 EUR 23209 EN ISSN 1018-5593 Luxembourg: Office for Official Publications of the European Communities © European Communities, 2008 Reproduction is authorised provided the source is acknowledged Printed in Italy Table of contents 1 BACKGROUND AND RATIONALE ....................................................................
    [Show full text]
  • General Ledger, Receivables Management, Payables Management, Sales Order Processing, Purchase Order Processing, and Invoicing
    Chapter 11: Revenue/Expense Deferrals setup Before you begin using Revenue/Expense Deferrals, you need to set the options you want to use for creating deferral transactions, such as the posting method used, and user access options. This information includes the following sections: • Revenue/Expense Deferrals overview • Deferral posting methods • Balance Sheet posting example • Profit and Loss posting example • Setting up revenue/expense deferrals • Selecting deferral warning options • Setting up a deferral profile • Setting access to a deferral profile Revenue/Expense Deferrals overview Revenue/Expense Deferrals simplifies deferring revenues or distributing expenses over a specified period. Revenue or expense entries can be made to future periods automatically from General Ledger, Receivables Management, Payables Management, Sales Order Processing, Purchase Order Processing, and Invoicing. If you use deferral transactions frequently, you can set up deferral profiles, which are templates of commonly deferred transactions. Using deferral profiles helps ensure that similar transactions are entered with the correct information. For example, if you routinely enter transactions for service contracts your company offers, and the revenue is recognized over a 12-month period, you could set up a deferral profile for these service contracts, specifying the accounts to be used, and the method for calculating how the deferred revenue is recognized. Deferral posting methods You can use two methods for posting the initial transactions and the deferral transactions: the Balance Sheet method, and the Profit and Loss method. Balance Sheet Using the Balance Sheet method, you’ll identify two posting accounts: a Balance Sheet deferral account to be used with the initial transaction for the deferred revenue or expense, and a Profit and Loss recognition account to be used with each period’s deferral transaction that recognizes the expense or revenue.
    [Show full text]
  • Models to Evaluate Service Provisioning Over Cloud
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Archives of the Faculty of Veterinary Medicine UFRGS Revista de Informatica´ Teorica´ e Aplicada - RITA - ISSN 2175-2745 Vol. 26, Num. 3 (2019) 65-74 RESEARCH ARTICLE Models to evaluate service Provisioning over Cloud Computing Environments - A Blockchain-As-A-Service case study Modelos para o provimento de Servic¸os em Ambientes de Computac¸ao˜ em Nuvem - Um estudo de caso aplicado a Blockchain como Servic¸o Carlos Melo1*, Jamilson Dantas2, Paulo Pereira3, Ronierison Maciel4, Paulo Maciel5 Abstract: The strictness of the Service Level Agreements (SLAs) is mainly due to a set of constraints related to performance and dependability attributes, such as availability. This paper shows that system’s availability values may be improved by deploying services over a private environment, which may obtain better availability values with improved management, security, and control. However, how much a company needs to afford to keep this improved availability? As an additional activity, this paper compares the obtained availability values with the infrastructure deployment expenses and establishes a cost × benefit relationship. As for the system’s evaluation technique, we choose modeling; while for the service used to demonstrate the models’ feasibility, the blockchain-as-a-service was the selected one. This paper proposes and evaluate four different infrastructures hosting blockchains: (i) baseline; (ii) double redundant; (iii) triple redundant, and (iv) hyper-converged. The obtained results pointed out that the hyper-converged architecture had an advantage over a full triple redundant environment regarding availability and deployment cost.
    [Show full text]
  • A Scoping Review of Integrated Blockchain-Cloud (Bcc) Architecture for Healthcare: Applications, Challenges and Solutions
    sensors Review A Scoping Review of Integrated Blockchain-Cloud (BcC) Architecture for Healthcare: Applications, Challenges and Solutions Leila Ismail 1,2,∗ , Huned Materwala 1,2 and Alain Hennebelle 3 1 Intelligent Distributed Computing and Systems Research Laboratory, Department of Computer Science and Software Engineering, College of Information Technology, United Arab Emirates University, Al Ain, Abu Dhabi 15551, United Arab Emirates; [email protected] 2 National Water and Energy Center, United Arab Emirates University, Al Ain, Abu Dhabi 15551, United Arab Emirates 3 Independent Researcher, Al Ain, Abu Dhabi 15551, United Arab Emirates; [email protected] * Correspondence: [email protected] Abstract: Blockchain is a disruptive technology for shaping the next era of a healthcare system striving for efficient and effective patient care. This is thanks to its peer-to-peer, secure, and transparent characteristics. On the other hand, cloud computing made its way into the healthcare system thanks to its elasticity and cost-efficiency nature. However, cloud-based systems fail to provide a secured and private patient-centric cohesive view to multiple healthcare stakeholders. In this situation, blockchain provides solutions to address security and privacy concerns of the cloud because of its decentralization feature combined with data security and privacy, while cloud provides solutions to the blockchain scalability and efficiency challenges. Therefore a novel paradigm of blockchain-cloud integration (BcC) emerges for the domain of healthcare. In this paper, we provide an in-depth Citation: Ismail, L.; Materwala, H.; analysis of the BcC integration for the healthcare system to give the readers the motivations behind Hennebelle, A.
    [Show full text]
  • Dealing with Granularity of Time in Temporal Databases
    DEALING WITH GRANULARITY OF TIME IN TEMPORAL DATABASES Gio Wiederhold t Department of Computer Science Stanford University, Stanford, CA 94305-2140, U.S.A. Sushil Jajodia Department of Information Systems and Systems Engineering George Mason University, Fairfax, VA 22030-4444, U.S.A. Witold Litwin* I.N.R.I.A. 78153 Le Chesnay, France ABSTRACT A question that always arises when dealing with temporal informa- tion is the granularity of the values in the domain type. Many different approaches have been proposed; however, the community has not yet come to a basic agree- ment. Most published temporal representations simplify the issue which leads to difficulties in practical applications. In this paper, we resolve the issue of temporal representation by requiring two domain types (event times and intervals), formal- ize useful temporal semantics, and extend the relational operations in such a way that temporal extensions fit into a relational representation. Under these considera- tions, a database system that deals with temporal data can not only present con- sistent temporal semantics to users but perform consistent computational sequences on temporal data from diverse sources. 1. Introduction Large databases do not just collect data about the current state of objects but retain infor- marion about past states as well. In the past, when storage was costly, such data was often not retained online. Aggregations of past information might have been kept, and detail data was archived. Certain applications always required that an adequate history be kept. In medical data- base systems a record of past events is necessary to avoid repeating ineffective or inappropriate treatments, and in other applications legal or planning requirements make keeping of a history desirable.
    [Show full text]
  • Time, Points and Space - Towards a Better Analysis of Wildlife Data in GIS
    Time, Points and Space - Towards a Better Analysis of Wildlife Data in GIS Dissertation zur Erlangung der naturwissenschaftlichen Doktorw¨urde (Dr. sc. nat.) vorgelegt der Mathematisch-naturwissenschaftlichen Fakult¨at der Universit¨at Z¨urich von Stephan Imfeld von Lungern OW Begutachtet von Prof. Dr. Kurt Brassel Prof. Dr. Bernhard Nievergelt Dr. Britta Allg¨ower Prof. Dr. Peter Fisher Z¨urich 2000 Die vorliegende Arbeit wurde von der Mathematisch-naturwissenschaftlichen Fakult¨at der Universit¨at Z¨urich auf Antrag von Prof. Dr. Kurt Brassel und Prof. Dr. Robert Weibel als Dissertation angenommen. How to Catch Running Animals with GIS and See What They’re up to i Abstract Geographical Information Systems are powerful instruments to analyse spatial data. Wildlife researchers and managers are always confronted with spatial data analysis and make use of these systems for various tasks. One important characteristic of the animals unter investigation is their locomotion. Thus the temporal aspects are important, but unfortunately GIS are almost ignorant concerning the analysis of the temporal domain. This thesis is trying to provide a new perspective on how to analyse moving point objects within GIS. A conceptual shift is performed from a space centered view to a way of analysing spatial and temporal aspects in an equally balanced way. For this purpose the family of analytical Time Plots was developed. They represent a completely new approach of how to analyse moving point objects. They transform the data originating from an animal’s movements into a repre- sentation with two time axes and one spatial axis that allows for an effective recognition of spatial patterns within the data.
    [Show full text]
  • Accelerating Software Delivery with Cloudbees
    BLOCKCHAIN-AS-A-SERVICE ACCELERATINGTaking POCs to production with SOFTWARE BlockApps and Red DELIVERY Hat WITH CLOUDBEES JENKINS & RED HAT OPENSTACK SOLUTION BRIEF SOLUTION BRIEF BLOCKAPPS EXPERIENCE BUILD AND TEST NEW ENTERPRISE BLOCKCHAIN APPS RAPIDLY • Over 1,000 BlockApps blockchain Pressure to meet the growing demands of international customers are driving financial services organi- projects in development zations to look for innovative software solutions to distinguish themselves in the marketplace. One of the • Over 100 enterprises building most significant technologies to emerge is the blockchain application, a disruptive shift in architecture solutions on BlockApps that will change how enterprises manage their data, applications, transactions, and business processes. • Contributing member of Ethereum developer community Until now, it has been costly to test and prove the value of blockchain applications in a secure, enterprise- ready environment built on proprietary software. Red Hat and BlockApps are removing those barriers. We have joined forces to help you build innovative proofs-of-concepts and enterprise-ready blockchain applications— RED HAT OPENSHIFT all running on Red Hat® Enterprise Linux® in an OpenShift container. BUSINESS VALUE According to IDC,1 Red Hat The BlockApps STRATO Blockchain Platform includes Ethereum-based features and tools that are designed OpenShift customers experienced: specifically for enterprise businesses to build proofs-of-concepts (POCs) quickly and cost-effectively. Using Red • 66% faster application Hat Enterprise Linux and Red Hat OpenShift Container Platform, you can seamlessly move from development development life cycles and test to full production of your blockchain applications. • 35% less IT staff per applications • 38% lower IT infrastructure costs per application BLOCKAPPPS STRATO BLOCKCHAIN PLATFORM The BlockApps STRATO Blockchain Platform offers customizable transaction processing capabilities and con- 1 IDC White Paper – “The Business Value of Red Hat OpenShift,” Oct.
    [Show full text]