Diploma thesis deals with design and creation of framework for modern web applications. The goal of the thesis is to create a fast, modern and modular MVC framework designed to create modern SPA-like web applications that has all the advantages of SPA but minimize or completely eliminate its disadvantages. The theoretical part explores existing MV* frameworks mainly from Node.js, but also from PHP or ASP.NET. It also deals with the analysis of the requirements for modern web frameworks to incorporate the technologies that are really used or replace bad or obsolete ones. The work itself deals with the design and implementation of the new MVC framework for Node.js, including the client part and some development support tools. An integral part of the thesis is the creation of a sample application in the created framework. At the end of the thesis there is summary of the created solution and the results of the comparison.

This diploma thesis deals with the development of web 2D HTML5 game, which users can play through a web browser. For the wide availability of games for various game devices (personal computers, game consoles, smartphones), the game is developed using modern web technologies. At the end of the work, the web game (application) was deployed and tested on the web.

The goal of the project is to evaluate three different methods of authenticating users on the Internet. These three methods are: login with username and password, two-factor authentication, and Freja eID. The login systems are evaluated in terms of usability, accessibility, security, and complexity. Usability and accessibility refer to how easy these systems are to use for different types of users and how well they work on various types of devices. This is determined through tests with programs and user tests. Security is evaluated through theory about Internet security, and complexity is measured by determining the cyclomatic complexity of the code. This means that the fewer paths there are through a code and the less complex these paths are, the less complex the code is. All code is written in JavaScript. Node.js was used for backend and Vue.js was used for frontend. A website has been constructed to test the login systems where the user can create an account, log in with password or two-factor authentication. In addition, there is a separate page for using the Freja eID's test API. The user tests that have been conducted show that testers preferred to log in with Freja eID and found it difficult to use two-factor authentication. Freja eID and two-factor authentication are considerably more secure than logging in with just a password and a username. In terms of code complexity, Freja eID was the solution that was the least complex and required the least amount of work. This makes Freja eID the solution that is ultimately recommended despite the cost per login. If a more economical alternative is desired, two-factor authentication is recommended. / Projektets mål är att utvärdera tre olika sätt att autentisera användare på Internet. Dessa tre sätt är inloggning med användarnamn och lösenord, tvåfaktorsautentisering och Freja eID. Inloggningssystemen utvärderas inom användbarhet, tillgänglighet, säkerhet och komplexitet. Användbarhet och tillgänglighet syftar till hur lätt dessa system är att använda för olika typer av användare och hur väl de fungerar på olika typer av enheter. Detta åstadkoms genom tester med program och användartester. Säkerheten utvärderas med hjälp av teori om säkerhet på Internet och komplexiteten mäts med hjälp av analys av den cyklomatiska komplexiteten i koden. Det innebär att ju färre vägar det finns genom en kod och ju mindre komplexa dessa vägar är, desto mindre komplex är koden. All kod är skriven i JavaScript. Node.js användes för backend och Vue.js användes för frontend. En webbplats har konstruerats för att testa inloggningssystemen där användaren kan skapa ett konto, logga in med lösenord eller tvåfaktorsautentisering. Dessutom finns det en separat sida för inloggning mot Freja eIDs test-API. De användartester som utförts visade att användare hade svårt att använda sig av tvåfaktorsautentisering och att inloggning med Freja eID var krångligare än inloggning med bara lösenord. När det gäller kodens komplexitet var Freja eID-lösningen den minst komplexa och krävde minst arbete. Det gör Freja eID till den rekommenderade lösningen trots att det kostar pengar vid varje inloggningstillfälle. Om man vill ha ett mer kostnadseffektivt alternativ rekommenderas tvåfaktorsautentisering.

This thesis describes a project that aimed to create a digital tool for use at a company. The tool performs a useful function that had been requested for a while by both management and the proposed users. The tool shows orders to be packed at the warehouse. The tool differs from the current system used in that it can show new orders placed in realtime instead of with the current systems delay. Wanted features were both ease of use in regards of quickly understanding the information, as well as information about the total workload. There is no interactivity, since the tool simply displays information. New queries to the existing database were tested, and problem solving was done to get the real-time aspect of the tool working correctly. The tool uses the existing database and technology similar to that of a simple web page, with a backend consisting of Node.js and NginX. The frontend for the project, which is the graphical presentation, uses HTML, CSS and JS. The result of this project was the actual tool in use by the company. It is used to see the total amount of orders as well as item counts for each order, on a day by day basis. Overall, the project was quite successful since the results were decent. However, some parts could be improved. / Denna uppsats beskriver ett projekt som handlade om att skapa ett digitalt verktyg hos ett företag. Verktyget fyller en funktion som efterfrågats länge av både företagets ledning och de som är användarna av verktyget. Det verktyget gör är att visa ordrar bestående av varor som ska packas på ett lager. Verktyget skiljer sig från det befintliga systemet på företaget i den aspekten att det kan visa nya inkommande ordrar i realtid, istället för med lång fördröjning.Önskemålen från ledningen och lagerarbetarna var att lätt kunna överblicka ordrar som finns, med information om hur mycket det finns att göra. Verktyget ska kunna användas utan interaktion från användarna, det ska alltså endast visa information.För att se ordrar i realtid så krävdes att nya databasfrågor testades, med problemlösning kring dessa. Verktyget använder sig av den befintliga databasen, och presenterar information på en skärm nära plockstationerna på lagret. Teknikerna som använts är de för en enkel webbsida, en backend med Node.js och NginX. Frontend för verktyget, alltså det grafiska gränssnittet, använder HTML, CSS och JS. Resultatet av projektet är verktyget som togs i drift på företagets lager. Verktyget används för att se antalet ordrar och artiklar per order, uppställt dag för dag. Projektet var lyckat, då ett bra resultat uppnåddes, dock finns förbättringspotential.

В данной работе проведено исследование для создания программного обеспечения управления контролем качества, позволяющего автоматизировать процесс оценки агентов, а также постановку задач менеджерам по контролю качества. Предметом исследования является разработка программного обеспечения, которое обеспечивает автоматизацию выбора взаимодействия агента и клиента, создание оценочных карт, отчетов о качестве, управление персоналом и многое другое. / In this work, a study was carried out to create a quality control management software that allows you to automate the process of evaluating agents, as well as setting tasks for quality control managers. The subject of the research is the development of software that automates the choice of interaction between the agent and the client, the creation of scorecards, quality reports, personnel management, and much more.

The goal of this study is to conduct a performance comparison betweenNode.js, Apache, Internet Information Services (IIS) and Go web servers in terms of throughput and memory consumption in both Input/Output (I/O)-intensive and computation-intensive situations. The computation-intensive tests consisted of calculating Fibonacci numbers, while the I/O-intensive tests consisted of querying a database. JMeter was used to send the requests and collect client- side data while Windows Performance Monitor was used to collect data on the resource use of the web servers on the server-side computer. The results showed that Go web server had the highest throughput and lowest memory consumption in all of the tests, with an average increase in throughput of 26% and an average decrease in memory consumption by 66% compared to the web servers placing second in the tests. IIS web server was the server that most often placed second behind Go. Contrary to previous studies Node.js performed worse than Apache in the I/O-intensive tests. The results also showed that Apache web server performed poorly in computation-intensive situations in terms of throughput. The conclusion is that the results indicate that Go web server performs better than Apache, IIS and Node.js web servers in both I/O- intensive and computation-intensive situations in terms of both throughput and memory consumption. / Denna studies mål är att genomföra en prestandajämförelse mellan Node.js, Apache, IIS och Go-webbservrar mätt i genomströmning och minnesallokering i både I/O-intensiva och beräkningsintensiva situationer. De beräkningsintensiva testerna bestod av att beräkna Fibonaccital medan de I/O-intensiva bestod av att be en databas om data. Programmet JMeter användes till att genomföra klientdatorns begäran till serverdatorn och till att samla data om begäran. Windows-programmet Performance Monitor användes till att samla data om webbservrarnas resursanvändning på serverdatorn. Resultaten visade att Go-webbservern hade högst genomströmmning och minst minnesallokering i alla tester med en genomströmmning som i genomsnitt var 26% högre och minnesallokering som var i genomsnitt 66% lägre än webbservrarna som presterade näst bäst i testerna. Webbservern som oftast presterade näst bäst var IIS. I motsats till resultaten i tidigare studier presterade Node.js sämre än Apache i de I/O-intensiva testerna. Apache visade sig prestera dåligt de beräkningsintensiva testerna. Studiens slutsats är att resultaten indikerar att Go-webbserver presterar bättre än Node.js, Apache och IIS-webbservrar i både I/O-intensiva och beräkningsintensiva situationer sett till genomströmning och minnesallokering.

Calculations have been a core part of business processes in several industries throughout the years. To streamline the process of calculations, companies seek to digitize their calculation tools to web-based calculation tools. There is currently a lack of studies regarding the performance of web-based calculation tools, and since technology changes occur rapidly, which leads to comparative studies becoming outdated, the availability of actual and relevant research regarding performance comparisons between web-development frameworks becomes imperative. The purpose of this study was to compare ASP.NET with Node.js Express performance-wise, while implemented as web-based calculation tools. The calculations implemented were placed in both the backend and frontend of ASP.NET and Node.js Express. This study consists of experimentation, presenting the experiment results, and analyzing the results to conclude the research questions of this study. The results showed that Node.js Express was the better framework performance-wise and the analysis explains why. This study also concluded that the backend was better performing than the frontend for calculations in ASP.NET, and that the frontend was better performing than the backend for calculations in Node.js Express.

Данная выпускная магистерская диссертация нацелена на разработку технологии нагрузочного тестирования локальной платежной системы для лиц с ограниченными возможностями здоровья. Актуальность состоит в непрерывной проверке системы на качество и стабильность работы приложения, в связи с отсутствием данного функционала, а также высокой стоимости у аналоговых сервисов. В работе решаются задачи: анализ потенциального количества пользователей, анализ аналогичных сервисов, анализ предметной области, реализация теоретической задачи разработки технологии нагрузочного тестирования для локальной платежной системы для людей с ограниченными возможностями здоровья, реализация проекта нагрузочного тестирования и мониторинга показателей системы, для снижения ресурсов. Объектом исследования является технология автоматизированного нагрузочного тестирования. Предмет исследования – процесс проведения нагрузочного тестирования в локальной платежной системе для лиц с ограниченными возможностями здоровья. Практическая значимость работы состоит разработке необходимого функционала приложения. Данный функционал поможет обычному человеку, без специальных знаний в программировании или разработке, понять на сколько система загружена и нуждается ли в доработке или увеличению мощности на удаленном сервере. Аналогичные проекты стоят дорого, обычному человеку разобраться с ними будет сложно. Так как проект социальный, как таковой прибыли с него получить нельзя, тем самым лишних денег на приобретение сторонних программ и найм специализированных людей на сопровождение системы нет. Экономический эффект работы состоит в сокращении финансовых затрат на проведение тестирования локальной платежной системы на всем жизненном цикле существования приложения. В связи с высокой стоимостью аналогичных разработок, а также высоким порогом вхождения, данная работа имеет большую актуальность. Полученный результат поможет сэкономить значительное количество финансов. / This graduate master's thesis is aimed at developing a technology for load testing of a local payment system for people with disabilities. The relevance consists in the continuous verification of the system for the quality and stability of the application, due to the lack of this functionality, as well as the high cost of analog services. The paper solves the following tasks: analysis of the potential number of users, analysis of similar services, domain analysis, implementation of the theoretical task of developing a load testing technology for a local payment system for people with disabilities, implementation of a load testing project and monitoring of system indicators to reduce resources. The object of the study is the technology of automated load testing. The subject of the study is the process of load testing in a local payment system for people with disabilities. The practical significance of the work consists in the development of the necessary application functionality. This functionality will help an ordinary person, without special knowledge in programming or development, to understand how much the system is loaded and whether it needs to be improved or increased capacity on a remote server. Similar projects are expensive, it will be difficult for an ordinary person to deal with them. Since the project is social, as such, it is impossible to get profit from it, thereby there is no extra money for the purchase of third-party programs and hiring specialized people to support the system. The economic effect of the work is to reduce the financial costs of testing the local payment system throughout the lifecycle of the application. Due to the high cost of similar developments, as well as the high entry threshold, this work is of great relevance. The result will help to save a significant amount of finance.

This paper delivers a comparative analysis of the performance of three of the NoSQL technologies in Web applications. These technologies are graph stores, key-value stores, and document stores. The study aims to assist developers and organizationsin picking the suitable NoSQL solution for their application. For this purpose, three identical e-book applications were developed. Each of these is connected to adatabase from the selected technologies to examine how they perform compared toeach other against various performance measures.

Context Considering the rising popularity of Node.js and the fact that a very largepercentage of websites today are based on PHP, there is a need to understand thesimilarities and differences between these languages.  Comparing their most popularserver-side  frameworks  is  valuable  to  developers  in  seeing  the  advantages  of  usingone over the other - for both user and developer. Objectives In this study we investigate how Express.js and Symfony compareagainst each other in terms of installation, functionality and performance. Thiswill provide understanding of when to use JavaScript frameworks and when to usePHP frameworks for server-side projects. Method A literature study was done to answer what similarities and differences existbetween the frameworks. To explore how they compare in performance when mul-tiple users are actively sending requests to the server, an experiment was performed.Another experiment was carried out to measure performance in CPU-intensive ap-plications. Results The result shows that both frameworks are quick to install and it is a fastprocess to setup a basic application. Both frameworks are highly cuztomizable andconfigurable because they are supported by a big open source community and theonly difference is that Express is supportive of single-page applications which Sym-fony can not do on its own. Express was better than Symfony to handle multipleconcurrent users when it comes to CPU usage and time it takes for the requests. For100 and 1000 requests, Express CPU usage varied more than Symfony, but at 10000and 100000 it varied less. In all tests with concurrent users, Express was faster. Testsperformed in the second experiment showed that Symfony is only able to use 1 corewhen making the requests while Express is able to use multiple cores. Even thoughSymfony was limited by 1 core it was faster, most likely because it used more memory. Conclusions This study shows that there are more similarities than differencesbetween Express and Symfony. They both strive for high customization and highflexibility with a goal to make tedious tasks easier for the developer. Both rely onopen source modules and components to add additional functionality. Out of thebox, Express comes with less functionality as it strives to be minimalistic. However,to install Symfony is slightly quicker than Express and requires no code. Thereare currently more daily downloads of Express than Symfony, and therefore it’sconsidered more popular. It’s supportive of JavaScript-only for front- and back-endand is able to handle more concurrent users than Symfony, and is therefore betterfor high-traffic websites. But Symfony is able to handle CPU-intensive applicationsbetter than Express, and is able to load in large data sets faster, making it a goodchoice for applications with a lot of data and high CPU usage.