Context. In recent years there is a rapid increase in demand for cloud services, as cloud computing has become a flexible platform for hosting micro services over the Internet.~Micro services are the core elements of service oriented architecture (SOA) that facilitate the deployment of distributed software systems.  Objectives. This thesis work aims at developing a typical service architecture to facilitate the deployment of compute and I/O intensive services. The thesis work also aims at evaluating the service times of these services when their respective sub services are deployed in heterogeneous environments with various loads. Methods. The thesis work has been carried out using an experimental test bed in order to evaluate the performance. The transport level performance metric called Response time is measured. It is the time taken by the server to serve the request sent by the client. Experiments have been conducted based on the objectives that are to be achieved. Results. The results obtained from the experimentation contain the average service times of a service when it is deployed on both virtual and non-virtual environments. The virtual environment is provided by Docker containers. They also include the variation in the position of their sub services. Conclusions. From results, it can be concluded that the total service times obtained are less in the case of non-virtual environment when compared to container environment.

Container technology has gained popularity in recent years, mainly because it enables a fast and easy way to package, distribute and deploy applications and services. Latency and throughput have a high impact on user satisfaction in many real-time, critical and large-scale online services. Although the use of microservices architecture in cloud-native applications has enabled advantages in terms of application resilience, scalability, fast software delivery and the use of minimal resources, the packet processing rates are not correspondingly higher. This is mainly due to the overhead imposed by the design and architecture of the network stack. Packet processing rates can be improved by making changes to the network stack and without necessarily adding more powerful hardware. In this research, a study of various high-speed packet processing frameworks is presented and a software high-speed packet I/O solution i.e., as hardware agnostic as possible to improve the packet throughput in container technology is identified. The proposed solution is identified based on if the solution involves making changes to the underlying hardware or not. The proposed solution is then evaluated in terms of packet throughput for different container networking modes. A comparison of the proposed solution with a simple UDP client-server application is also presented for different container networking modes. From the results obtained, it is concluded that packet mmap client-server application has higher performance when compared with simple UDP client-server application.

The aim of this study has been to determine whether Microsoft Azure Service Bus has been able to match the needs and demands of Sogeti and its clients during a transition to a distributed and service-oriented system, as well as investi- gate possible gains that can be attained from such a transition. The study has also critically examined the potential problems and difficulties that may arise in such a scenario. The study has been accomplished using a literature study as well as the development of a Proof-of-Concept model to simulate such a system and to make calculations and surveys of and within one. The survey has shown that the Azure Service Bus does match the pre-defined requirements and requisites, as well as demonstrated how safe communication can be guaranteed using this particular service bus. The study concludes with an analysis of the study as a whole and the results thereof in particular, as well as proposes measures for further research on the subject. Finally, recommendations are made on how the client should proceed based on what is found in the study. / Målet med denna studie har varit att utröna huruvida Microsoft Azure Service Bus har kunnat matcha de behov och krav som Sogeti och dess klienter har på en sådan vid en övergång till ett distribuerat tjänsteorienterat system, samt undersöka vilka eventuella vinster som finns att göra vid en sådan övergång. Studien har också kritiskt granskat de problem och svårigheter som kan komma att uppstå. Undersökningen har gjorts med hjälp av en litteraturstudie samt en utveckling av en Proof-of-Concept-modell för att simulera ett sådant system och för att kunna göra beräkningar och undersökningar av och inom ett sådant. Undersökningen har visat att Azure Service Bus matchar de krav och önskemål som på förhand ställts, samt visat på hur säker kommunikation kan garanteras med hjälp av denna servicebuss. Undersökningen avslutas med en analys av studien som helhet och resultatet i synnerhet, samt föreslår åtgärder vid vidare forskning inom ämnet. Avslutningsvis lämnas rekommendationer på hur uppdragsgivaren ska gå tillväga baserat på vad som i studien framkommer.

Microservices is an architectural technique that has only gotten more popular as the need for scalable and performant internet-based applications has grown. One of the characteristics of microservices is communication through lightweight protocols like HTTP. These protocols are usually provided through frameworks that enable an abstracted form of communication and when implementing services using the Go language, the most common frameworks are gRPC and net/http. The aim of this thesis is to evaluate and compare the performance and usability of gRPC and HTTP frameworks in order to determine which one is better suited for microservices so that developers can be empowered to be more informed when making choices about their technology. We investigated the performance and usability by conducting two experiments. For the first one, we created two services that were implemented as identically as possible using Go but one communicated using the net/http framework and the other using gRPC. The services implemented methods that return small, medium, and large payload sizes and were then load-tested at varying numbers of virtual users. The second experiment was conducted by recruiting a set of participants that were tasked with completing two sets of coding tasks once using gRPC and once using HTTP. After the tasks were completed they were asked to fill out a questionnaire to measure their experience using the frameworks, the answers were then turned into a score which we could use to analyze the frameworks. The results from the performance experiment indicated that gRPC performed better in terms of throughput and latency, while HTTP performed better in scalability, and the results from the usability experiment indicated that HTTP was found to be more usable by the participants.

Tourism is an important factor for economic growth. Unfortunately, the on going COVID-19 pandemic has struck hard on the tourism sector due to the lockdowns and travel restrictions. The lockdowns have also led to an increasing isolation among people which in the long term can lead to a decline in people’s psychological wellbeing.Together with Cybercom Group AB, an idea to solve this problem was to developan application with the intention to nurture the tourism sector and get people out of their homes while keeping the human interactions at a satisfactory level. The main feature of the application developed was a scheduler that carefully planned out people’s daily activities depending how crowded a specific location was. An application such as the one developed could lead to an increase in foot traffic while simultaneously decreasing the amount of physical contact between people. The result of this thesis mainly focuses on the developed application but more specifically the developed algorithms to schedule your day using crowd data. The algorithmdeveloped, the Optimal Time Slot Algorithm, averaged a crowding value of18,8% while the average of the best possible crowding value was 17,8%. / Turism är en viktig faktor för ekonomisk tillväxt. Tyvärr så har den pågående COVID-19 pandemin slagit hårt mot turismsektorn till följd av nedstängningar och restriktionerpå resande. Nedstängningarna har även lett till en ökad isolering hos personersom långsiktigt kan leda till en försämring av människors psykologiska välmående.Tillsammans med Cybercom Group AB växte en idé fram om att utveckla enapplikation som har till uppgift att främja turismsektorn och hjälpa folk att ta sig utur sina hem samtidigt som de undviker trängsel. Huvudfunktionen hos den utvecklade applikationen var en planerare som noggrantplanerar en persons dagliga aktiviteter beroende på hur mycket folk det var på denspecifika platsen vid ett visst tillfälle. En applikation likt den som utvecklats kan ledatill en ökad mängd personer i rörelse i kombination med att minska mängden fysiskkontakt mellan människor. Resultatet av detta examensarbete fokuserar huvudsakligen på den utvecklade applikationenoch specifikt de algoritmer som utvecklats för att planera din dag genomträngseldata. Den framtagna algoritmen, Optimal Time Slot Algorithm, resulteradei ett trängselsnitt på 17,8% där 18,8% var snittet av det bästa möjliga resultatet.

Micro Frontends är en ny mjukvarusystemarkitektur som påstås lösa många av problemen som drabbar monolitiska frontends med stora kodbaser. Den begränsade andelen forskning som undersökt konceptet har nått motsägelsefulla slutsatser kring arkitekturens effekt i praktiken. Detta är problematiskt då många företag överväger att migrera till arkitekturen men är tveksamma, vilket motiveras av den bristande kunskapen om konceptet. Denna kvantitativa studie ämnar undersöka om utvecklare som jobbar med Micro Frontends upplever dess fördelar och nackdelar genom att jämföra deras upplevelse med utvecklare som jobbar med en monolitisk frontend. Datan samlades in genom en surveyundersökning och analyserades med statistiska metoder. Resultaten av den kvantitativa analysen visade att kodduplicering samt att hålla ett UX konsekvent är problematiska aspekter vid användandet av Micro Frontends. Studiens låga svarsfrekvens gör att dessa resultat inte anses som generaliserbara. / Micro Frontends is a new software system architecture that is said to solve many of the problems that exist in monolithic frontends with large codebases. The limited amount of research that has examined the concept have reached contradictory conclusions about the effect of the architecture in practice. This is problematic as many companies are considering migrating to the Micro Frontend architecture but are hesitant, which is motivated by the lack of knowledge about the concept. This quantitative study aims to investigate whether developers working with Micro Frontends experience its theorized advantages and disadvantages by comparing their experience with developers working with a monolithic frontend. The data were collected through a survey and analyzed using statistical methods. The results of the quantitative analysis showed that code duplication and keeping a consistent UX is problematic when using Micro Frontends. The study's low response rate however means that these results are not considered generalizable.

В данной работе рассматривается проблема отсутствия автоматизации некоторых бизнес-процессов, в связи с чем затягивается время обслуживание клиентов банка. Было проведено исследование в области ЭДО, архитектуры систем, всевозможных межсистемных интеграций. Были описаны сценарии, определены точки входа, последовательность шагов в новом бизнес-процессе, выделены требования для нового процесса. Полученный результат вынесен на рассмотрение для выделения времени средств на его разработку. / In this paper, the problem of the lack of automation of some business processes is considered, which is why the bank's customer service time is delayed. A solution is proposed in the form of designing a new business process that would combine several old business processes using electronic document management technologies. A study was conducted in the field of EDI, system architecture, and all kinds of intersystem integrations. Scenarios were described, entry points were identified, the sequence of steps in the new business process, and requirements for the new process were highlighted. The result has been submitted for consideration in order to allocate time and funds for its development.

No description available.

Flera företag använder sig än idag av mjukvarusystem som är uppbyggda med äldre mjukvaruarkitektur som den monolitiska. Ett av dessa företag är Consid vars personalsystem är uppbyggt med det utdaterade ramverket klassisk ASP och där användargränssnitt samt logik kan direkt kommunicera med varandra. Detta medför begränsningar som uppstår till följd av brister i modularitet på grund av valet av mjukvaruarkitektur, vilket försvårar vidareutveckling och ändringar i ett system. Dessa begränsningar påverkar i sin tur parametrar som prestanda, skalbarhet, säkerhet, robusthet samt integrering med modernare tekniker.  I denna rapport presenteras en litteraturstudie samt en semistrukturerad intervjustudie, i syfte att undersöka vilka mjukvaruarkitekturer som är lämpliga att implementera vid en modernisering av en monolitisk mjukvaruarkitektur. Arbetet diskuterade också vilka utmaningar som kan uppstå vid en sådan modernisering och hur de hanteras på ett effektivt sätt. Ett bedömningsschema med önskvärda parametrar, med avseende på skalbarhet, prestanda, säkerhet och robusthet, togs fram för att underlätta avgörandet vid val av mjukvaruarkitektur. Utifrån detta, beslutades det att en prototyp med en REST-baserad arkitektur skulle implementeras och utvärderas.  Resultatet av prototypen, till följd av re-architecting, visade en ökad modularisering av mjukvaruarkitekturen. I jämförelse mot med det tidigare systemet har den nya prototypen ingen större påverkan på prestanda i form av responstid. Däremot bidrog prototypen till förbättrad skalbarhet när det gäller vidareutvecklingen av systemet, eftersom det förenklar införandet av ny funktionalitet. Prototypen hade också högre säkerhet genom att isolera lager ifrån varandra samt dölja underliggande detaljer i implementationen. Dessutom blev prototypen inte bara mer robust till följd av modulariseringen, men även enklare att utföra integrationstester samt destruktiva tester mot. / Several companies still use software systems that are built with older software architecture such as the monolithic one. One of these companies is Consid, whose personnel system is built with the outdated framework Classic ASP and where the user interface and logic can directly communicate with each other. This entails limitations that arise because of shortcomings in modularity due to the choice of software architecture, which complicates further development and changes in a system. These limitations in turn, affect parameters such as performance, scalability, security, robustness, and integration with modern technologies. In this work, a literature study was conducted as well as a semi-structured interview study in order to investigate which software architectures are suitable to implement when a modernization of a monolithic software architecture, is carried out. The work also discussed the challenges that may arise in a modernization of the software architecture and how they are handled efficiently. An assessment scheme with desirable parameters regarding scalability, performance, security, and robustness, was developed to facilitate the decision in the choice of software architecture. Based on this, it was decided that a prototype with a REST-based architecture would be implemented and evaluated. The result of the prototype, following re-architecting, showed an increased modularization of the software architecture. Compared to the previous system, the new prototype has no major impact on performance in terms of response time. However, the prototype contributed to better scalability in the further development of the system as it simplifies the introduction of new functionality. The prototype also had higher security by isolating layers from each other and hiding the underlying details in the implementation. In addition, the prototype not only became more robust because of the modularization, but also easier to perform destructive tests against.