DatalogBlocks: Relational Logic Integration Patterns

Ritter, Daniel; Bross, Jan

doi:10.1007/978-3-319-10085-2_29

Cited by 1 publication

(2 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We argue that integration operations, represented by Enterprise Integration Patterns (EIP) [9], can be mapped to an "in-memory" representation of the table-centric RDBMS operations to profit from their efficient and fast evaluation. Early ideas on this were brought up in our position papers [11,12]. In this work, we follow up to shed light on the observed discrepancies.…”

Section: Introductionmentioning

confidence: 74%

“…The application of table-centric operators to current integration systems has not been considered before, up to our knowledge, and was only recently introduced by our position paper [12], which discusses the expressiveness of table-centric / logic programming for integration processing on the content level. The work on Java systems like Telegraph Dataflow [15], and Jaguar [18]) can be considered related work in the area of programming languages on application systems for faster, data-aware processing.…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Towards More Data-Aware Application Integration

Ritter

2015

Data Science

Self Cite

View full text Add to dashboard Cite

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.

show abstract

Section: Introductionmentioning

confidence: 74%

Section: Related Workmentioning

confidence: 99%