1
0

overleaf edits
Some checks failed
continuous-integration/drone/push Build is passing
continuous-integration/drone/tag Build is failing

This commit is contained in:
2020-10-28 10:46:16 +01:00
parent 9f5aface07
commit fe30555762
13 changed files with 515 additions and 195 deletions

View File

@@ -5,12 +5,120 @@
title = {Comparing Virtual Machines vs Docker Containers}
}
@INPROCEEDINGS{8875447, author={H. {Chen} and F. J. {Lin}}, booktitle={2019 International Conference on Internet of Things (iThings) and IEEE Green Computing and Communications (GreenCom) and IEEE Cyber, Physical and Social Computing (CPSCom) and IEEE Smart Data (SmartData)}, title={Scalable IoT/M2M Platforms Based on Kubernetes-Enabled NFV MANO Architecture}, year={2019}, volume={}, number={}, pages={1106-1111}, doi={10.1109/iThings/GreenCom/CPSCom/SmartData.2019.00188}}
@article{doi:10.1002/wsb.529,
author = {Mahjoub, Ghazi and Hinders, Mark K. and Swaddle, John P.},
title = {Using a “sonic net” to deter pest bird species: Excluding European starlings from food sources by disrupting their acoustic communication},
journal = {Wildlife Society Bulletin},
volume = {39},
number = {2},
pages = {326-333},
keywords = {acoustic masking, alarm call, bird strike, deterrent, noise pollution, parametric array, predation risk, starling, Sturnus vulgaris},
doi = {10.1002/wsb.529},
url = {https://wildlife.onlinelibrary.wiley.com/doi/abs/10.1002/wsb.529},
eprint = {https://wildlife.onlinelibrary.wiley.com/doi/pdf/10.1002/wsb.529},
abstract = {ABSTRACT Pest avian wildlife is responsible for substantial economic damage every year in the United States. Previous technologies used to deter starlings have generally failed because birds quickly habituate to startle regimes. In this study, conducted from May to July 2013, we focused on altering the foraging behavior of the European starling (Sturnus vulgaris), a pest bird that is responsible for crop losses and also poses notable risk for birdaircraft strikes. The goal of our project was to develop an effective system to limit starlings' use of a food patch. Using nonlinear ultrasonic parametric arrays, we broadcast a directional sound that overlapped in frequency with starling vocalizations and was contained in a specific area, creating a “net.” We hypothesized that the “sonic net” would disturb acoustic communication for starlings, causing them to leave and feed elsewhere. Using wild-caught starlings in a large aviary, we deployed the sonic net over one food patch while leaving another food patch unaltered, and assessed their presence and feeding for three consecutive days. The sonic treatment decreased starlings' presence at the treated food patch, on average by 46\%. Additionally, we assessed whether the sonic net disrupted the birds' response to an alarm call. When under the sonic net, starlings did not respond to the alarm call, suggesting that the sonic net disrupted acoustic communication. The sonic net is a promising new method of decreasing foraging activity by pest bird species. © 2015 The Wildlife Society.},
year = {2015}
}
@inproceedings{10.1145/3341105.3373875,
author = {Grambow, Martin and Meusel, Lukas and Wittern, Erik and Bermbach, David},
title = {Benchmarking Microservice Performance: A Pattern-Based Approach},
year = {2020},
isbn = {9781450368667},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
url = {https://doi.org/10.1145/3341105.3373875},
doi = {10.1145/3341105.3373875},
abstract = {Benchmarking microservices serves to understand and check their non-functional properties for relevant workloads and over time. Performing benchmarks, however, can be costly: each microservice requires the design and implementation of a benchmark, possibly repeatedly as the service evolves. As microservice APIs differ, benchmarking tools that assume common interfaces - like ones for databases - do not exist.In this work, we present a pattern-based approach to reduce the efforts for defining microservice benchmarks, while still allowing to measure qualities of complex interactions. It assumes that microservices expose a REST API, described in a machine-understandable way, and allows developers to model interaction patterns from abstract operations that can be mapped to that API. Possible data-dependencies between operations are resolved at runtime. We implement a prototype of our approach, which we use to demonstrate that it can be applied to open-source microservices with little effort. Our work shows that pattern-based benchmarking of microservices is feasible and opens up opportunities for microservice providers and tooling developers.},
booktitle = {Proceedings of the 35th Annual ACM Symposium on Applied Computing},
pages = {232241},
numpages = {10},
location = {Brno, Czech Republic},
series = {SAC '20}
}
@INPROCEEDINGS{6449437, author={P. {Leitner} and C. {Inzinger} and W. {Hummer} and B. {Satzger} and S. {Dustdar}}, booktitle={2012 Fifth IEEE International Conference on Service-Oriented Computing and Applications (SOCA)}, title={Application-level performance monitoring of cloud services based on the complex event processing paradigm}, year={2012}, volume={}, number={}, pages={1-8}, doi={10.1109/SOCA.2012.6449437}}
@INPROCEEDINGS{7968049, author={C. M. {Aderaldo} and N. C. {Mendonça} and C. {Pahl} and P. {Jamshidi}}, booktitle={2017 IEEE/ACM 1st International Workshop on Establishing the Community-Wide Infrastructure for Architecture-Based Software Engineering (ECASE)}, title={Benchmark Requirements for Microservices Architecture Research}, year={2017}, volume={}, number={}, pages={8-13}, doi={10.1109/ECASE.2017.4}}
@INPROCEEDINGS{8486300, author={Y. {Niu} and F. {Liu} and Z. {Li}}, booktitle={IEEE INFOCOM 2018 - IEEE Conference on Computer Communications}, title={Load Balancing Across Microservices}, year={2018}, volume={}, number={}, pages={198-206}, doi={10.1109/INFOCOM.2018.8486300}}
@INPROCEEDINGS{7557535, author={S. {Hassan} and R. {Bahsoon}}, booktitle={2016 IEEE International Conference on Services Computing (SCC)}, title={Microservices and Their Design Trade-Offs: A Self-Adaptive Roadmap}, year={2016}, volume={}, number={}, pages={813-818}, doi={10.1109/SCC.2016.113}}
@INPROCEEDINGS{6778179, author={M. {Aazam} and I. {Khan} and A. A. {Alsaffar} and E. {Huh}}, booktitle={Proceedings of 2014 11th International Bhurban Conference on Applied Sciences Technology (IBCAST) Islamabad, Pakistan, 14th - 18th January, 2014}, title={Cloud of Things: Integrating Internet of Things and cloud computing and the issues involved}, year={2014}, volume={}, number={}, pages={414-419}, doi={10.1109/IBCAST.2014.6778179}}
@InProceedings{10.1007/978-3-319-29504-6_7,
author="Oweis, Nour E.
and Aracenay, Claudio
and George, Waseem
and Oweis, Mona
and Soori, Hussein
and Snasel, Vaclav",
editor="Abraham, Ajith
and Wegrzyn-Wolska, Katarzyna
and Hassanien, Aboul Ella
and Snasel, Vaclav
and Alimi, Adel M.",
title="Internet of Things: Overview, Sources, Applications and Challenges",
booktitle="Proceedings of the Second International Afro-European Conference for Industrial Advancement AECIA 2015",
year="2016",
publisher="Springer International Publishing",
address="Cham",
pages="57--67",
abstract="Nowadays, Internet of Things (IoT) is growing rapidly. Billions of devices are expected to be associated in the coming future. Smart and sensing devices have impacted the Big Data area through huge data generation and gathering during the communication between new physical object. The challenges in this communication process can be seen in the necessity to handle huge amount of data that can serve different purposes in various fields such as, medical, social, commercial, industrial and scientific fields. This study aims at presenting some of the most recent advances in IoT. We divided the study into four main parts: short history, Big Data concept, IoT sources (hardware and software), and finally some challenges and future expectations. The objective of the study is to give readers an updated description of the IoT and its impact on Big Data.",
isbn="978-3-319-29504-6"
}
@misc{docker-overview,
howpublished = {\url{https://docs.docker.com/engine/docker-overview/}},
note = {Megtekintve 2020-02-22},
title = {Docker overview}
}
@misc{pycurl-comparison,
howpublished = {\url{https://github.com/svanoort/python-client-benchmarks}},
note = {Megtekintve 2020-05-24},
title = {Microbenchmark of different python HTTP clients}
}
@INPROCEEDINGS{7321603, author={A. {Poniszewska-Maranda} and D. {Kaczmarek}}, booktitle={2015 Federated Conference on Computer Science and Information Systems (FedCSIS)}, title={Selected methods of artificial intelligence for Internet of Things conception}, year={2015}, volume={}, number={}, pages={1343-1348}, doi={10.15439/2015F161}}
@Article{Opara-Martins2016,
author={Opara-Martins, Justice
and Sahandi, Reza
and Tian, Feng},
title={Critical analysis of vendor lock-in and its impact on cloud computing migration: a business perspective},
journal={Journal of Cloud Computing},
year={2016},
month={Apr},
day={15},
volume={5},
number={1},
pages={4},
abstract={Vendor lock-in is a major barrier to the adoption of cloud computing, due to the lack of standardization. Current solutions and efforts tackling the vendor lock-in problem are predominantly technology-oriented. Limited studies exist to analyse and highlight the complexity of vendor lock-in problem in the cloud environment. Consequently, most customers are unaware of proprietary standards which inhibit interoperability and portability of applications when taking services from vendors. This paper provides a critical analysis of the vendor lock-in problem, from a business perspective. A survey based on qualitative and quantitative approaches conducted in this study has identified the main risk factors that give rise to lock-in situations. The analysis of our survey of 114 participants shows that, as computing resources migrate from on-premise to the cloud, the vendor lock-in problem is exacerbated. Furthermore, the findings exemplify the importance of interoperability, portability and standards in cloud computing. A number of strategies are proposed on how to avoid and mitigate lock-in risks when migrating to cloud computing. The strategies relate to contracts, selection of vendors that support standardised formats and protocols regarding standard data structures and APIs, developing awareness of commonalities and dependencies among cloud-based solutions. We strongly believe that the implementation of these strategies has a great potential to reduce the risks of vendor lock-in.},
issn={2192-113X},
doi={10.1186/s13677-016-0054-z},
url={https://doi.org/10.1186/s13677-016-0054-z}
}
@misc{iot-hub-azure,
howpublished = {\url{https://docs.microsoft.com/hu-hu/azure/iot-hub/about-iot-hub}},
note = {Megtekintve 2020-03-25},
title = {Mi az Azure IoT Hub?}
}
@misc{stream-hub-azure,
howpublished = {\url{https://docs.microsoft.com/hu-hu/azure/stream-analytics/stream-analytics-introduction}},
note = {Megtekintve 2020-03-25},
title = {Mi az az Azure Stream Analytics?}
}
@misc{linux-namespaces,
howpublished = {\url{http://man7.org/linux/man-pages/man7/namespaces.7.html}},
note = {Megtekintve 2020-02-20},
@@ -30,6 +138,14 @@
title = {A microservice architekt{\'u}r{\'a}r{\'o}l di{\'o}h{\'e}jban}
}
@misc{kristofmsc,
author = {Nagy Krist{\'o}f},
howpublished = {\url{https://diplomaterv.vik.bme.hu/hu/Theses/Tomeges-gepgep-kommunikacio-mezogazdasagi}},
note = {MSc Diplomaterv, BME-VIK, 2020},
title = {Tömeges g{\'e}p-g{\'e}p kommunik{\'a}ci{\'o} mezőgazdas{\'a}gi alkalmaz{\'a}sa}
}
@misc{kubernetes-pods,
howpublished = {\url{https://kubernetes.io/docs/concepts/workloads/pods/pod/}},
note = {Megtekintve 2020-02-21},
@@ -400,3 +516,17 @@
title = {Time series database (TSDB) explained}
}
@book{Goodfellow-et-al-2016,
title={Deep Learning},
author={Ian Goodfellow and Yoshua Bengio and Aaron Courville},
publisher={MIT Press},
note={\url{http://www.deeplearningbook.org}},
year={2016}
}
@misc{cousins-of-artificial-intelligence,
howpublished = {\url{https://towardsdatascience.com/cousins-of-artificial-intelligence-dda4edc27b55}},
note = {Megtekintve 2020-10-27},
title = {Cousins of Artificial Intelligence},
author = {Seema Singh}
}