Ivan Borodii
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Research Subjects
Ivan Borodii has a total of 5 co-authors. Here are the top co-authors by number of shared publications:
- Diana Velychko
Rochester Institute of Technology, Rochester, USA
1 shared publication Halyna Osukhivska
1 shared publication- Halyna Osukhivska
Ternopil Ivan Puluj National Technical University
1 shared publication - Illia Fedorovych
Ternopil Ivan Puluj National Technical University 56 Ruska St UA46001 Ternopil Ukraine
1 shared publication - Roman Butsiy
Institute of Telecommunications and Global Information Space of the National Academy of Sciences of Ukraine
1 shared publication
Latest Publications
- 7 October 2026
- Published by Metascience in Bulletin of Cherkasy State Technological University
- Vol. 31 (3) , 11-21
Architecture of hybrid Edge Lakehouse for environmental monitoring on Raspberry Pi
In this article, a hybrid Edge Lakehouse architecture for environmental monitoring is presented, which has been implemented and experimentally tested on a Raspberry Pi 5 edge device. The relevance of the research is driven by the need for a robust edge computing architecture that supports local collection, processing and transactional storage of sensor data, followed by synchronisation with a cloud-based analytics environment, within the limitations of hardware resources. The main objective of this work was to develop the Edge Lakehouse architecture as a local component of an autonomous monitoring system and to evaluate its performance. In this study, experimental modelling of the hardware-software system was conducted, along with measurements of execution time, memory usage and Central Processing Unit load, as well as an assessment of resilience to forced power shutdowns and temporary network outages. The proposed hybrid Edge Lakehouse architecture maintains data integrity and operational continuity under emergency and unstable conditions, as confirmed by experimental studies. In particular, the results showed that the average processing time for a single micro-batch of sensor data was 25.51 seconds, of which 20.04 seconds were spent on initialising the processing environment, 1.18 seconds on writing to the local table and 3.94 seconds on synchronising with the cloud environment. The system demonstrated correct recovery without loss of confirmed data and the 48-hour replication window allowed for autonomous synchronisation recovery without duplicate records. The obtained data also confirmed the architecture’s suitability for long-term autonomous functioning. The proposed solutions have practical value as a reliable local layer for autonomous environmental monitoring systems
- 7 October 2026
- Published by Metascience in Bulletin of Cherkasy State Technological University
- Vol. 31 (3) , 11-21
Architecture of hybrid Edge Lakehouse for environmental monitoring on Raspberry Pi
In this article, a hybrid Edge Lakehouse architecture for environmental monitoring is presented, which has been implemented and experimentally tested on a Raspberry Pi 5 edge device. The relevance of the research is driven by the need for a robust edge computing architecture that supports local collection, processing and transactional storage of sensor data, followed by synchronisation with a cloud-based analytics environment, within the limitations of hardware resources. The main objective of this work was to develop the Edge Lakehouse architecture as a local component of an autonomous monitoring system and to evaluate its performance. In this study, experimental modelling of the hardware-software system was conducted, along with measurements of execution time, memory usage and Central Processing Unit load, as well as an assessment of resilience to forced power shutdowns and temporary network outages. The proposed hybrid Edge Lakehouse architecture maintains data integrity and operational continuity under emergency and unstable conditions, as confirmed by experimental studies. In particular, the results showed that the average processing time for a single micro-batch of sensor data was 25.51 seconds, of which 20.04 seconds were spent on initialising the processing environment, 1.18 seconds on writing to the local table and 3.94 seconds on synchronising with the cloud environment. The system demonstrated correct recovery without loss of confirmed data and the 48-hour replication window allowed for autonomous synchronisation recovery without duplicate records. The obtained data also confirmed the architecture’s suitability for long-term autonomous functioning. The proposed solutions have practical value as a reliable local layer for autonomous environmental monitoring systems
- Open Access
Comparative analysis of large data processing in Apache Spark using Java, Python and Scala
During the study, the results of a comparative analysis of the process of handling large datasets using the Apache Spark platform in Java, Python, and Scala programming languages were obtained. Although prior works have focused on individual stages, comprehensive comparisons of full ETL workflows across programming languages using Apache Iceberg remain limited. The analysis was performed by executing several operations, including downloading data from CSV files, transforming and loading it into an Apache Iceberg analytical table. It was found that the performance of the Spark algorithm varies significantly depending on the amount of data and the programming language used. When processing a 5-megabyte CSV file, the best result was achieved in Python: 6.71 seconds, which is superior to Scala's score of 9.13 seconds and Java's time of 9.62 seconds. For processing a large CSV file of 1.6 gigabytes, all programming languages demonstrated similar results: the fastest performance was showed in Python: 46.34 seconds, while Scala and Java showed results of 47.72 and 50.56 seconds, respectively. When performing a more complex operation that involved combining two CSV files into a single dataset for further loading into an Apache Iceberg table, Scala demonstrated the highest performance, at 374.42 seconds. Java processing was completed in 379.8 seconds, while Python was the least efficient, with a runtime of 398.32 seconds. It follows that the programming language significantly affects the efficiency of data processing by the Apache Spark algorithm, with Scala and Java being more productive for processing large amounts of data and complex operations, while Python demonstrates an advantage in working with small amounts of data. The results obtained can be useful for optimizing data handling processes depending on specific performance requirements and the amount of information being processed.
Open AccessComparative analysis of large data processing in Apache Spark using Java, Python and Scala
During the study, the results of a comparative analysis of the process of handling large datasets using the Apache Spark platform in Java, Python, and Scala programming languages were obtained. Although prior works have focused on individual stages, comprehensive comparisons of full ETL workflows across programming languages using Apache Iceberg remain limited. The analysis was performed by executing several operations, including downloading data from CSV files, transforming and loading it into an Apache Iceberg analytical table. It was found that the performance of the Spark algorithm varies significantly depending on the amount of data and the programming language used. When processing a 5-megabyte CSV file, the best result was achieved in Python: 6.71 seconds, which is superior to Scala's score of 9.13 seconds and Java's time of 9.62 seconds. For processing a large CSV file of 1.6 gigabytes, all programming languages demonstrated similar results: the fastest performance was showed in Python: 46.34 seconds, while Scala and Java showed results of 47.72 and 50.56 seconds, respectively. When performing a more complex operation that involved combining two CSV files into a single dataset for further loading into an Apache Iceberg table, Scala demonstrated the highest performance, at 374.42 seconds. Java processing was completed in 379.8 seconds, while Python was the least efficient, with a runtime of 398.32 seconds. It follows that the programming language significantly affects the efficiency of data processing by the Apache Spark algorithm, with Scala and Java being more productive for processing large amounts of data and complex operations, while Python demonstrates an advantage in working with small amounts of data. The results obtained can be useful for optimizing data handling processes depending on specific performance requirements and the amount of information being processed.