Searcharxiv⌕ Search

arXiv subjects

Daniel Ritter

Publications and source records attributed to Daniel Ritter.

31 records · Page 2Linked to original sources

A Rule-based Language for Application Integration

Although message-based (business) application integration is based on orchestrated message flows, current modeling languages exclusively cover (parts of) the control flow, while under-specifying the data flow. Especially for more data-intensive integration scenarios, this fact adds to the inherent data processing weakness in conventional integration systems. We argue that with a more data-centric integration language and a relational logic based implementation of integration semantics, optimizations from the data management domain(e.g., data partitioning, parallelization) can be combined with common integration processing (e.g., scatter/gather, splitter/gather). With the Logic Integration Language (LiLa) we redefine integration logic tailored for data-intensive processing and propose a novel approach to data-centric integration modeling, from which we derive the control-and data flow and apply them to a conventional integration system.

cs.DB↗

Non-Relational Databases on FPGAs: Survey, Design Decisions, Challenges

Non-relational database systems (NRDS), such as graph, document, key-value, and wide-column, have gained much attention in various trending (business) application domains like smart logistics, social network analysis, and medical applications, due to their data model variety and scalability. The broad data variety and sheer size of datasets pose unique challenges for the system design and runtime (incl. power consumption). While CPU performance scaling becomes increasingly more difficult, we argue that NRDS can benefit from adding field programmable gate arrays (FPGAs) as accelerators. However, FPGA-accelerated NRDS have not been systematically studied, yet. To facilitate understanding of this emerging domain, we explore the fit of FPGA acceleration for NRDS with a focus on data model variety. We define the term NRDS class as a group of non-relational database systems supporting the same data model. This survey describes and categorizes the inherent differences and non-trivial trade-offs of relevant NRDS classes as well as their commonalities in the context of common design decisions when building such a system with FPGAs. For example, we found in the literature that for key-value stores the FPGA should be placed into the system as a smart network interface card (SmartNIC) to benefit from direct access of the FPGA to the network. However, more complex data models and processing of other classes (e.g., graph and document) commonly require more elaborate near-data or socket accelerator placements where the FPGA respectively has the only or shared access to main memory. Across the different classes, FPGAs can be used as communication layer or for acceleration of operators and data access. We close with open research and engineering challenges to outline the future of FPGA-accelerated NRDS.

cs.DB↗

Financial Contagion in a Generalized Stochastic Block Model

One of the most defining features of the global financial network is its inherent complex and intertwined structure. From the perspective of systemic risk it is important to understand the influence of this network structure on default contagion. Using sparse random graphs to model the financial network, asymptotic methods turned out powerful to analytically describe the contagion process and to make statements about resilience. So far, however, they have been limited to so-called {\em rank one} models in which informally the only network parameter is the degree sequence (see (Amini et. al. 2016) and (Detering et. al. 2019) for example) and the contagion process can be described by a one dimensional fix-point equation. These networks fail to account for a pronounced block structure such as core/periphery or a network composed of different connected blocks for different countries. We present a much more general model here, where we distinguish vertices (institutions) of different types and let edge probabilities and exposures depend on the types of both, the receiving and the sending vertex plus additional parameters. Our main result allows to compute explicitly the systemic damage caused by some initial local shock event, and we derive a complete characterisation of resilient respectively non-resilient financial systems. This is the first instance that default contagion is rigorously studied in a model outside the class of rank one models and several technical challenges arise. Moreover, in contrast to previous work, in which networks could be classified as resilient or non resilient, independent of the distribution of the shock, information about the shock becomes important in our model and a more refined resilience condition arises. Among other applications of our theory we derive resilience conditions for the global network based on subnetwork conditions only.

q-fin.RM↗

Mathematical Modeling of Systemic Risk in Financial Networks: Managing Default Contagion and Fire Sales

As impressively shown by the financial crisis in 2007/08, contagion effects in financial networks harbor a great threat for the stability of the entire system. Without sufficient capital requirements for banks and other financial institutions, shocks that are locally confined at first can spread through the entire system and be significantly amplified by various contagion channels. The aim of this thesis is thus to investigate in detail two selected contagion channels of this so-called systemic risk, provide mathematical models and derive consequences for the systemic risk management of financial institutions. The first contagion channel we consider is default contagion. The underlying effect is here that insolvent institutions cannot service their debt or other financial obligations anymore - at least partially. Debtors and other directly impacted parties in the system are thus forced to write off their losses and can possibly be driven into insolvency themselves due to their incurred financial losses. This on the other hand starts a new round in the default contagion process. In our model we simplistically describe each institution by all the financial positions it is exposed to as well as its initial capital. In doing so, our starting point is the work of Detering et al. (2017) - a model for contagion in unweighted networks - which particularly considers the exact network configuration to be random and derives asymptotic results for large networks. We extend this model such that weighted networks can be considered and an application to financial networks becomes possible. More precisely, for any given initial shock we deduce an explicit asymptotic expression for the total damage caused in the system by contagion and provide a necessary and sufficient criterion for an unshocked financial system to be stable against small shocks. Moreover, ...

q-fin.RM↗

Catalog of Formalized Application Integration Patterns

Enterprise application integration (EAI) solutions are the centrepiece of current enterprise IT architectures (e.g., cloud and mobile computing, business networks), however, require the formalization of their building blocks, represented by integration patterns, verification and optimization. This work serves as an instructive pattern formalization catalog that leads to the formalization of all currently known integration patterns. Therefore, we explain the classification of the underlying requirements of the pattern semantics and formalize representative patterns from the different categories, by realizing them in timed db-net. In this way, the catalog will allow for the addition of future patterns by assigning them to a category and applying the described formalism.

cs.SE↗

Catalog of Optimization Strategies and Realizations for Composed Integration Patterns

The discipline of Enterprise Application Integration (EAI) is the centrepiece of current on-premise, cloud and device integration scenarios. However, the building blocks of integration scenarios, i.e., essentially a composition of Enterprise Integration Patterns (EIPs), are only informally described, and thus their composition takes place in an informal, ad-hoc manner. This leads to several issues including a currently missing optimization of application integration scenarios. In this work, we collect and briefly explain the usage of process optimizations from the literature for integration scenario processes as catalog.

cs.SE↗

Toward A Collection of Cloud Integration Patterns

Cloud computing is one of the most exciting IT trends nowadays. It poses several challenges on application integration with respect to, for example, security. In this work we collect and categorize several new integration patterns and pattern solutions with a focus on cloud integration requirements. Their evidence and examples are based on extensive literature and system reviews.

cs.SE↗

Towards More Data-Aware Application Integration (extended version)

Although most business application data is stored in relational databases, programming languages and wire formats in integration middleware systems are not table-centric. Due to costly format conversions, data-shipments and faster computation, the trend is to "push-down" the integration operations closer to the storage representation. We address the alternative case of defining declarative, table-centric integration semantics within standard integration systems. For that, we replace the current operator implementations for the well-known Enterprise Integration Patterns by equivalent "in-memory" table processing, and show a practical realization in a conventional integration system for a non-reliable, "data-intensive" messaging example. The results of the runtime analysis show that table-centric processing is promising already in standard, "single-record" message routing and transformations, and can potentially excel the message throughput for "multi-record" table messages.

cs.DB↗

Qualitative Analysis of Integration Adapter Modeling

Integration Adapters are a fundamental part of an integration system, since they provide (business) applications access to its messaging channel. However, their modeling and configuration remain under-represented. In previous work, the integration control and data flow syntax and semantics have been expressed in the Business Process Model and Notation (BPMN) as a semantic model for message-based integration, while adapter and the related quality of service modeling were left for further studies. In this work we specify common adapter capabilities and derive general modeling patterns, for which we define a compliant representation in BPMN. The patterns extend previous work by the adapter flow, evaluated syntactically and semantically for common adapter characteristics.

cs.SE↗

Using the Business Process Model and Notation for Modeling Enterprise Integration Patterns

Enterprise Integration Patterns (EIP) are a collection of widely used stencils for integrating enterprise applications and business processes. These patterns represent a "de-facto" standard reference for design decisions when integrating enterprise applications. For each of these patterns we present the integration semantics (model) and the conceptual translation (syntax) to the Business Process Model and Notation (BPMN), which is a "de-facto" standard for modelling business process semantics and their runtime behavior.

cs.SE↗

Towards Connected Enterprises: The Business Network System

The discovery, representation and reconstruction of Business Networks (BN) from Network Mining (NM) raw data is a difficult problem for enterprises. This is due to huge amounts of complex business processes within and across enterprise boundaries, heterogeneous technology stacks, and fragmented data. To remain competitive, visibility into the enterprise and partner networks on different, interrelated abstraction levels is desirable. We present a novel data discovery, mining and network inference system, called Business Network System (BNS), that reconstructs the BN--integration and business process networks--from raw data, hidden in the enterprises' landscapes. BNS provides a new, declarative foundation for gathering information, defining a network model, inferring the network and check its conformance to the real-world "as-is" network. The paper covers both the foundation and the key features of BNS, including its underlying technologies, its overall system architecture, and its most interesting capabilities.

cs.DB↗

Advanced Data Processing in the Business Network System

The discovery, representation and reconstruction of Business Networks (BN) from Network Mining (NM) raw data is a difficult problem for enterprises. This is due to huge amounts of e.g. complex business processes within and across enterprise boundaries, heterogeneous technology stacks, and fragmented data. To remain competitive, visibility into the enterprise and partner networks on different, interrelated abstraction levels is desirable. We show the query and data processing capabilities of a novel data discovery, mining and network inference system, called Business Network System (BNS) that reconstructs the BN--integration and business process networks - from raw data, hidden in the enterprises' landscapes. The paper covers both the foundation and the key data processing characteristics features of BNS, including its underlying technologies, its overall system architecture, and data provenance approach.

cs.OH↗

A Logic Programming Approach to Integration Network Inference

The discovery, representation and reconstruction of (technical) integration networks from Network Mining (NM) raw data is a difficult problem for enterprises. This is due to large and complex IT landscapes within and across enterprise boundaries, heterogeneous technology stacks, and fragmented data. To remain competitive, visibility into the enterprise and partner IT networks on different, interrelated abstraction levels is desirable. We present an approach to represent and reconstruct the integration networks from NM raw data using logic programming based on first-order logic. The raw data expressed as integration network model is represented as facts, on which rules are applied to reconstruct the network. We have built a system that is used to apply this approach to real-world enterprise landscapes and we report on our experience with this system.

cs.DB↗