With almost 70% of the population being active internet users and with signs that this number only will increase in the coming years, the value for companies, organisations, and hobbyists to be able to share what is important to them will also increase. One of the most common ways to gain attraction on the internet is with the help of a website. There are multiple ways to create a website, with one popular approach is with the help of content managing systems (CMS). Different CMSs offer a range of functionality and range in complexity. A staple name in the CMS community is Drupal. Drupal can provide the entirety of an application but can also be used in a decoupled mode where it serves as the backend for a frontend developed with other technologies, e.g. a JavaScript library like ReactJS. This thesis aimed to evaluate how the JavaScript library ReactJS interacted with Drupal when used in its decoupled mode. Different methods, such as JSON:API and GraphQL, to export data from the Drupal site were also compared. The thesis also aimed to guide less experienced developers through their journey of decoupled CMSs. Through extensive research about Drupal and ReactJS, as well as the core functionalities, the thesis provides the necessary groundwork for implementing a decoupled application. The concepts are then further expanded with realistic examples to provide a deeper understanding of the subject. By implementing a realist web application containing common functionalities found in modern web applications, it could be concluded that Drupal and ReactJS complemented each other excellently by providing each other with features the other one did not have. Difficulties encountered were related to the unique technologies rather than their collaboration. The comparison between JSON:API and GraphQL elucidated clear benefits and drawbacks for each, providing a guide for developers to choose based on their specific needs. Future research could broaden the scope to other CMSs and JavaScript libraries to enhance the understanding of decoupled architecture. Exploring the implementation of custom APIs is also suggested for further studies.

As databases and traffic over the internet is becoming larger by the day, the performance of sending information has become a target of great importance. In past years, other software architectural styles such as REST have been used as it is a reliable framework and works really well when one has a dependable internet connection. In 2015, the querying language GraphQL was released by Facebook to the public as an alternative to REST. GraphQL made improvements in fetching data by for example removing the possibility of under- and overfitting. This means that a client only gets the data which they have requested, nothing more, nothing less. To create a GraphQL schema and server implementation requires time, effort and knowledge. This is however a requirement to run GraphQL over your current legacy database. For this reason multiple server implementation tools have been created by vendors to reduce development time and instead auto-generates a GraphQL schema and server implementation using an already existing database. This bachelor thesis will pick, run and compare the benchmarks of the two different server implementation tools Hasura and PostGraphile. This is done using a benchmark methodology based on technical difficulties (choke points). The result of our benchmark suggests that the throughput is larger for Hasura compared to PostGraphile whilst the query execution time as well as query response time is similar. PostGraphile is better at paging without offset as well as ordering, but on all other cases Hasura outperforms PostGraphile or shows similar results. / Linköping GraphQL Benchmark (LinGBM)

Med dagens snabba utveckling av informationsteknologin och med ökningen av antalet människor som är uppkopplade mot Internet, blir utvecklingen av webbtjänster allt viktigare. Eftersom webbtjänster har en betydande roll för utvecklingen av Internet, uppstår frågan om vilka verktyg som bör användas för att uppnå den prestanda som dagens användare kräver. Ett vanligt tillvägagångssätt för implementering av webbtjänster är med arkitekturen REST. Dock har REST prestandasvagheter som overfetching, underfetching och hantering av slutpunkter som uppstår i fall där flera slutpunkter nås. Ett alternativ till REST är frågespråket GraphQL som utvecklades för att utesluta de svagheter som REST har och således förbättra prestanda vid datahämtning. I detta arbete utfördes prestandamätningar där latens och datavolym mättes vid olika typer av frågor för respektive GraphQL, REST utan cache och REST med cache. Latens är tidsintervallet från att en klient skickar en förfrågan till att klienten mottar svaret, och datavolym avser storleken på data i ett svarspaket som överförs från en server till en klient. REST med cache togs med i prestandamätningarna då det inte har undersökts i tidigare arbeten som jämfört prestanda mellan GraphQL och REST. Resultaten visade att GraphQL presterar bättre med avseende på både latens och datavolym, i jämförelse med de övriga systemen i fall där förfrågningar ställs mot två eller flera slutpunkter i REST. GraphQL presterade sämre än övriga system, med avseende på latens, när endast en slutpunkt i REST kontaktades. Däremot presterade GraphQL bättre än de övriga systemen, med avseende på datavolym, i samtliga fall. Vid jämförelse av REST med och utan cache visade det sig att ju fler slutpunkter som kontaktades, desto bättre presterade REST utan cache med avseende på datavolym medan REST med cache presterade bättre med avseende på latens. / With today’s rapid development of information technology and with the increase in the number of people connected to the Internet, the development of web services is becoming more important. As web services play a significant role in the development of the Internet, the question arises as to which tools should be used to achieve the performance required by today’s users. A common approach for implementing web services is with the architecture REST. However, REST has performance weaknesses such as overfetching, underfetching, and maintenance of endpoints, that arise in cases where multiple endpoints are accessed. An alternative to REST is the GraphQL query language, which was developed to exclude the weaknesses that REST has and thus improve performance in data retrieval. In this work, performance measurements were conducted where latency and data volume were measured for different types of queries for GraphQL, REST without cache and, REST with cache. Latency is the time interval between a client sending a request and the client receiving the response, and data volume refers to the size of data in a response packet that is transmitted from a server to a client. REST with cache was included in the experiment as it has not been investigated in previous work comparing performance between GraphQL and REST. The results showed that GraphQL performs better, in terms of both latency and data volume, compared to the other systems in cases where requests are made to two or more endpoints in REST. GraphQL performed worse than the other systems, in terms of latency, when only one endpoint in REST was contacted. However, GraphQL performed better than the other systems in terms of data volume in all cases. When comparing REST with and without cache, it turned out that the more endpoints that were contacted, the better REST without cache performed in terms of data volume, while REST with cache performed better in terms of latency.

The main purpose of this report is to analyse and suggest suitable implementation of information system Justimio, which would be used by Justmighty, a company operataning on the Czech digital market, mainly oriented on internet marketing. The master thesis is divided into three parts. The first part is focused on the analyse of the theoretical knowledge and its related possibilities. Due to the usage of professional methods, the current situation can be analysed and the web applications position in the environment of the closest competitors can be recorded. In second chapter, a focus is also given to the company Justmighty, for which the application is made for. A company’s ability to implement this application is checked by using a basic analytical methods, whereas also can be analysed how this application would be helpful, when comes to the competitors and current market. The last part is focused on possible solutions and implementation of information system Justimio.

Modern applications commonly make use of several subsystems, usually a frontend and a backend. The communication link between these subsystems is commonly an API. Different APIs such as REST and SOAP have been around for a long time but with the increasing use of internet, other techniques as GraphQL have been developed to compensate for older techniques. The aim of this thesis is to measure the performance of GraphQL and how it compares to SOAP and REST and how the overhead reduction of GraphQL will affect the performance. The main method used to evaluate the performance differences between GraphQL, REST and SOAP is an experiment. The results show that GraphQL has the worst performance in all test cases. GraphQL has the lowest packet size out of all three APIs when only a few fields are fetched, however the packet size increases rapidly when multiple fields are requested.

The purpose of this study is to compare the two architectural techniques REST and GraphQL. This thesis will compare the two techniques and what defines them. A literature study and experimental study are carried out by the researchers. Four applications have been developed that include the ability to disable and to enable caching for both technologies to test the performance effect of caching. Earlier work has not covered the effects on caching related to these two frameworks. The literature study results point to that REST services are up to date and GraphQL is a technique with a shorter history, but that has declared growth in the industry and is a well suited choice for example when bandwidth matters in mobile phone applications. In the experimental study the tests showed slightly better results on average for REST API in terms of total response time (ms). Depending on the intended project there are many factors that need to be evaluated before making a decision on which framework to use.

Dagens samhälle är beroende av internet och webbapplikationer för olika uppgifter. Svarstiden för API:er spelar en avgörande roll i responsiviteten för webbapplikationer. Två huvudsakliga API-tillvägagångssätt, GraphQL och REST, har sina egna styrkor och svagheter. Studien syftar till att jämföra svarstider för GraphQL och REST API:er och undersöka minneskapaciteten hos Raspberry Pi och Ubuntu som serverarkitekturer. En artefakt byggs för att agera som API och mätverktyg. Resultaten kommer att ha betydelse för datavetenskapen och ha praktiska implikationer för webbutvecklare och användare. Mätningar visar att REST har snabbare svarstider vid enskilda anrop medan GraphQL är snabbare vid underfetching, och minnesprestandan mellan Raspberry Pi och Ubuntu visar ingen signifikant skillnad.

Modern web applications are growing in complexity and becoming more widely used. Using frameworks to build APIs is a popular way for both hobby developers and businesses to speed up development time and save costs. With this dependence on frameworks to be the foundation for potentially large applications comes the need to understand their performance qualities and which areas they are best suited for. This study compares the performance of the two similarly popular frameworks ASP.NET Core and Express.js, when used together with a MySQL Database to build Web APIs. This was done by building two different API implementations in each framework, one employing a RESTful approach and the other using the new querying language GraphQL. Experiments were run where the peak CPU usage, peak memory usage and response times were measured.The results of the experiments were that in a RESTful API, ASP.NET Core is faster at serving requests during lower loads whereas Express.js outperforms ASP.NET Core when faced with a higher amount of concurrent requests that fetch a lot of data. In a GraphQL API Express.js was able to perform similarly or better in all cases in terms of response times and resource usage compared to ASP.NET Core.

The purpose of the project is to create a website where Knowit Experience can present and invite people to their coding events. The work has been carried out by a larger team including project managers, UX designers, supervisors, and an Agile approach has been used. A Headless CMS called Hygraph has been used to create a structure that editors can easily use, and this CMS includes a GraphQL API that the website consumes. The website is created in React with TypeScript to create a secure typed application styled with Sass. The website handles registrations for newsletters and different event lists from users and displays the content of the editors. Several different user flows on the website have been automated using Pipedream to make it easier for editors, including automatic confirmation emails sent to those who register, and editors can easily send emails to specific mailing lists. Structure is also created in the CMS to allow editors to create dynamic forms to collect opinions and information from visitors at an event. The website has been developed with accessibility in mind and has been tested on different browsers and devices. The website is continuously tested for accessibility and correctly validated code throughout the work. The work results in a fully functional website with all intended features. / Projektets syfte är att skapa en webbplats där Knowit Experience kan presentera och bjuda in till deras event Kodkvällar. Arbetet har utförts i ett större team med projektledare, UX-designers samt handledare och arbetssättet har vart Agilt. Ett Headless CMS, Hygraph, har använts för att skapa en struktur som redaktörer enkelt kan använda och med detta CMS ingår ett GraphQL API som webbplatsen konsumerar. Webbplatsen skapas i React med TypeScript för att skapa en säker typad applikation som stylas med Sass. Webbplatsen hanterar anmälningar till nyhetsbrev och olika eventlistor från användare samt visar redaktörernas innehåll. Med Pipedream har flera olika användarflöden på webbplatsen automatiserats för att underlätta för redaktörerna. Bland annat skickas bekräftelsemail automatiskt till de som anmäler sig samt att redaktörer enkelt kan skicka ut mail till specifika maillistor. Struktur skapas även i CMSet för att redaktörer ska kunna skapa dynamiska formulär för att inhämta åsikter och information från besökarna på ett event. Webbplatsen har utvecklats med tillgänglighet i åtanke och den har testats i olika webbläsare samt på olika enheter. Webbplatsen testas kontinuerligt för tillgänglighet samt korrekt validerande kod genom hela arbetet. Arbetet resulterar i en fullt fungerande webbplats med alla tänkta funktioner.

GraphQL is a database handling API created by Facebook, that provides an effective al-ternative to REST-style architectures. GraphQL provides the ability for a client to spec-ify exactly what data it wishes to receive. A problem with GraphQL is that the freedomof creating customized requests allows data to be included several times in the response,growing the response’s size exponentially. The thesis contributes to the field of GraphQLanalysis by studying the prevalence of simple cycles in GraphQL schemas. We have im-plemented a locally-run tool and webtool using Tarjan’s and Johnson’s algorithms, thatparses the schemas, creates a directed graph and enumerates all simple cycles in the graph.A collection of schemas was analysed with the tool to collect empirical data. It was foundthat 39.73 % of the total 2094 schemas contained at least one simple cycle, with the averagenumber of cycles per schema being 4. The runtime was found to be on average 11 mil-liseconds, most of which consisted of the time for parsing the schemas. It was found that44 out of the considered schemas could not be enumerated due to containing a staggeringamount of simple cycles. It can be concluded that it is possible to test schemas for cyclicityand enumerate all simple cycles in a given schema efficiently.