Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Reducing the Effort on Backward Compatibility in Cloud Servers
Blekinge Institute of Technology, Faculty of Computing, Department of Computer Science and Engineering. (Computer Science)
2017 (English)Independent thesis Advanced level (degree of Master (Two Years)), 20 credits / 30 HE creditsStudent thesis
Abstract [en]

The Big Enterprises all over the world are setting up their services in cloud as this is cheaper and offers a lot of other benefits. These services have to be updated from time to time and for this, the enterprises have to upgrade their systems in the cloud. During these upgrades, the enterprises face a lot of problems known as compatibility issues. The companies are investing big time to avoid these compatibility issues. The investment could be in money, time, labor etc. also known as effort. Therefore, it is in our interest to attempt to reduce this effort. In this study, our main objectives are to calculate the effort required to maintain the backward compatibility during the upgrade process in the cloud and to find ways to reduce this effort. Reducing the effort will help the companies cut down their investment. A hypothesis was introduced saying that the network usage was dependent on the upgrade method chosen.

We have chosen experimentation to be the suitable research method. To run our experiments, we have created a virtual environment similar to that of Ericsson. The experimental values were recorded. We recorded the values such as code complexity, total time for the upgrade process and the network usage during the experiment. Using these values, we tried to estimate the effort and scale it to real time scenarios. Using ANOVA we proved that our null hypothesis was correct. The results have then been discussed in detail and RQ1 is answered. Later RQ2 is answered based on the answer for RQ1. Through our analysis we were able to get a rough estimate of the effort (labor, time, cost) required to maintain backward compatibility. We propose that the existence of the tool mentioned will reduce the effort considerably. The features of the tool are explained in detail. Some future work as the actual development of the tool has been suggested.

Place, publisher, year, edition, pages
2017. , 55 p.
Keyword [en]
Upgrades, Backward Compatibility, Avro
National Category
Computer Science
Identifiers
URN: urn:nbn:se:bth-14029OAI: oai:DiVA.org:bth-14029DiVA: diva2:1082875
External cooperation
Ericsson
Subject / course
DV2566 Master's Thesis (120 credits) in Computer Science
Educational program
DVAXA Master of Science Programme in Computer Science
Presentation
2016-09-28, J1630, Blekinge Institute of Technology SE-371 79 Karlskrona, Sweden, Karlskrona, 13:00 (English)
Supervisors
Examiners
Available from: 2017-03-23 Created: 2017-03-19 Last updated: 2017-03-23Bibliographically approved

Open Access in DiVA

fulltext(675 kB)29 downloads
File information
File name FULLTEXT02.pdfFile size 675 kBChecksum SHA-512
25af886b18b2b8fcadf4ab8382e56071519a5119b7a71e2b65e162dbed38ad142498d918941aca7d220af3494c533c643c82d8fcfba3470f8fdac391947bf855
Type fulltextMimetype application/pdf

By organisation
Department of Computer Science and Engineering
Computer Science

Search outside of DiVA

GoogleGoogle Scholar
Total: 29 downloads
The number of downloads is the sum of all downloads of full texts. It may include eg previous versions that are now no longer available

Total: 107 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf