Skip to main navigation Skip to search Skip to main content

An experimental study of fog and cloud computing in CEP-based Real-Time IoT applications

  • Giovanny Mondragón-Ruiz
  • , Alonso Tenorio-Trigoso
  • , Manuel Castillo-Cara
  • , Blanca Caminero
  • , Carmen Carrión

Research output: Contribution to journalArticle (Contribution to Journal)peer-review

37 Scopus citations

Abstract

Internet of Things (IoT) has posed new requirements to the underlying processing architecture, specially for real-time applications, such as event-detection services. Complex Event Processing (CEP) engines provide a powerful tool to implement these services. Fog computing has raised as a solution to support IoT real-time applications, in contrast to the Cloud-based approach. This work is aimed at analysing a CEP-based Fog architecture for real-time IoT applications that uses a publish-subscribe protocol. A testbed has been developed with low-cost and local resources to verify the suitability of CEP-engines to low-cost computing resources. To assess performance we have analysed the effectiveness and cost of the proposal in terms of latency and resource usage, respectively. Results show that the fog computing architecture reduces event-detection latencies up to 35%, while the available computing resources are being used more efficiently, when compared to a Cloud deployment. Performance evaluation also identifies the communication between the CEP-engine and the final users as the most time consuming component of latency. Moreover, the latency analysis concludes that the time required by CEP-engine is related to the compute resources, but is nonlinear dependent of the number of things connected.

Original languageEnglish
Article number1
Pages (from-to)32
Number of pages1
JournalJournal of Cloud Computing
Volume10
Issue number1
DOIs
StatePublished - 7 Jun 2021

Fingerprint

Dive into the research topics of 'An experimental study of fog and cloud computing in CEP-based Real-Time IoT applications'. Together they form a unique fingerprint.

Cite this