Systems
Darmstadt, Germany (June 24-28)
Over the past decade, the ACM International Conference on Distributed
and Event-based Systems (DEBS) has become the premier venue for academia
and industry to discuss cutting-edge research of event-based computing
related to Big Data, AI/ML, IoT and Distributed Systems. The objectives
of the ACM International Conference on Distributed and Event-Based
Systems (DEBS) are to provide a forum dedicated to the dissemination of
original research, the discussion of practical insights, and the
reporting of experiences relevant to distributed systems and event-based
computing. The conference aims at providing a forum for academia and
industry to exchange ideas.
Research Track
=====
The DEBS conference covers topics in distributed and event-based
computing. The scope of the conference includes systems dealing with
collecting, detecting, processing and responding to events through
distributed middleware and applications. Examples of application domains
covered by the conference include the Internet of Things, sensor
networks, social networking, finance, healthcare and logistics, computer
and network security. Technologies discussed include real-time
analytics, complex-event detection, reliability and resilience, energy
management and green computing, data stream processing, big/fast data
analysis, event processing for AI/ML, AI/ML for event processing,
security and encryption in stream processing, embedded systems, and
cloud, peer-to-peer, ubiquitous and mobile computing. Topics relevant to
enterprise-level computing include enterprise application integration,
real-time enterprises, Web services and support for enterprises to
respond in timely fashion to changing situations.
Topics covered include, but are not limited to:
- Models, architectures and paradigms: Event-driven architectures,
real-time analytics, complex event processing, event processing for
AI/ML, event processing in big and fast data, data stream processing,
security and encryption in stream processing, rule-based systems,
in-network processing, logic-based event recognition, event correlation
and pattern languages.
- Systems and software: Distributed data processing, distributed
programming, federated event-based systems, AI/ML for event processing,
information-centric networking, software-defined networking, security,
reliability and resilience, programmable hardware, energy management and
green computing as well as cloud, fog, ubiquitous and mobile computing.
- Applications: Use cases, requirements and applications of distributed
and event-based systems in various domains including Internet-of-Things,
cyber-physical systems, sensor networks, social networking, multimedia
analytics, finance, healthcare and logistics, computer and network
security, smart contracts and blockchains. Also, relevant topics span
enterprise-level computing, including enterprise application
integration, real-time enterprises, event-based business process
management, and support for enterprises to respond in timely fashion to
changing situations.
Industry and Experience Reports Track
=========
The DEBS 2019 Industry and Experience Reports Track invites submissions
on innovative design, development, or deployments of event-based
systems. Contributions will be reviewed by researchers and industry
practitioners working in distributed and event-based computing.
An important goal of DEBS is to enrich and cultivate cooperation and
exchange between researchers and practitioners who work on distributed
or event-based systems. Such interactions help practitioners become
aware of leading edge research that can address issues and problems in
commercial systems, while also allowing researchers to learn more about
details and concerns with event-based or distributed applications and
systems that arise in commercial implementations and deployments.
We welcome submissions in the form of either a full Industry Track paper
or an Industry Experience report. Submissions should present novel work
and experiences with relevant topics including, but not limited to, the
following:
- Use cases and applications of event-based or distributed approaches
- Models, architectures and paradigms of event-driven or distributed systems
- Hardware acceleration (e.g., GPUs, FPGAs) for event-based or
distributed systems
- Cloud-based infrastructure (VMs or containers) for event-based or
distributed systems
- Distributed systems trade-offs for event-based applications
- Event-based or distributed systems reliability and fault tolerance
- Event-based or distributed systems transactional support
- Event-based or distributed systems security considerations
- Programming languages and DSLs for event-based or distributed systems
- Deploying and operating event-based or distributed systems
- Event-based or distributed systems in emerging domains (e.g.,
personalized health, machine learning)
- Testing and benchmarking of real-world, event-based or distributed systems
Important Dates
===============
Abstract submission research track: Mar 08th, 2019
Research and industry paper submission: Mar 08th, 2019
Tutorial proposal submission: Mar 22nd, 2019
Grand Challenge solution submission: Apr 07th, 2019
Author Notification (Research & Industry track): Apr 19th, 2019
Poster, Demo, Doctoral Workshop submission: Apr 22nd, 2019
Camera Ready Versions of Paper: May 14th, 2019
Submissions
===========
All submissions must be original and unpublished. Accepted papers will
be published by ACM and disseminated through the ACM Digital Library.
Authors Take Note: A new policy by ACM will allow DEBS 2019 to make the
proceedings available ahead of the conference via the ACM Digital
Library. Thus, the official publication date is the date the proceedings
appear in the ACM Digital Library. This date may be up to two weeks
prior to the first day of the conference. The official publication date
affects the deadline for any patent filings related to published work.
The conference adopts a double-blind review process for the research
track, where neither authors nor reviewers know each other's identities.
This means that papers must not list or otherwise identify the authors.
References to previous work should be done in the third person as to not
reveal the identities of the authors. Research track submissions that
are not anonymous may be rejected without review.
Research Track papers must be no longer than 12 pages. The authors of
accepted papers will be given a choice between different copyright
agreements, in accordance with the recent changes in the ACM policy. The
options will include new opportunities for open access as well as the
traditional ACM copyright agreement. Further information about the
submissions can be found on the web page with submission information.
Submissions to the research track will be evaluated by a Research
Program Committee, listed here:
http://www.debs2019.org/committees/Program_Committee.html
Submissions to the Industry Track should clearly indicate whether they
are an Industry Track Paper or an Industry Experience Report. Industry
Track papers should cover some novel use or development of event-based
applications or distributed systems, with an industry theme, and must be
no longer than 12 pages. Industry Experience Reports can be specific to
a single project or system, or to an industry domain, and should cover
some valuable, new or alternative view of event processing or
distributed systems in an end-user application area. Industry Experience
reports are in the form of extended abstracts, do not need to be full
papers, and must be no longer than 6 pages.
An Industry Program Committee will review all submissions to the
Industry Track using a single-blind process, unlike the double-blind
reviews in the Research Track, so information about the authors and
their affiliations should be present in all submissions.
--
Dr. rer. nat. Ruben Mayer
Chair of Application and Middleware Systems (Informatics 13)
Technical University of Munich
**********************************************************
*
* Contributions to be spread via DMANET are submitted to
*
* DMANET@zpr.uni-koeln.de
*
* Replies to a message carried on DMANET should NOT be
* addressed to DMANET but to the original sender. The
* original sender, however, is invited to prepare an
* update of the replies received and to communicate it
* via DMANET.
*
* DISCRETE MATHEMATICS AND ALGORITHMS NETWORK (DMANET)
* http://www.zaik.uni-koeln.de/AFS/publications/dmanet/
*
**********************************************************
Posts
