Papers › Choosing an effective setup for stream processing
Choosing an effective setup for stream processing
Federico Ruilova, Aleksandar Yonchev
The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.
This project aims to study the feasibility and cost-effectiveness of using edge computing for stream data processing in the context of Internet of Things (IoT) in manufacturing in Europe. Two scenarios were considered: using edge computing to reduce latency and using a popular public cloud provider. Both scenarios demonstrated high throughput, with the edge computing scenario slightly outperforming the public cloud scenario. The impact on resource utilization was also measured, with the edge node showing slightly lower resource usage than the cloud node. The experiment concluded that running the system at the edge is more cost-efficient, but only using any Infrastructure as a Service (IaaS) provider acting as the infrastructure provider. IaaS providers will be crucial in offering edge solutions and identifying geographical areas where regional data centers could be used as points of presence for low-latency applications. Keywords: edge computing, stream data processing, Internet of Things (IoT), manufacturing, Europe, latency, throughput, resource utilization, cost-efficiency, infrastructure as a service (IaaS), regional data centers, low-latency applications, cloud computing, feasibility study.
Code
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
Code Syntology ran Syntology
Not run by Syntology. Nothing on this page verifies that the listed code works.
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections