OVERVIEW OF POPULAR APPROACHES IN CREATING CLIENT-SERVER APPLICATIONS BASED ON SCIENTOMETRICS ONAFTS’ PLATFORM

D. Salskyi, A. Kozhukhar, O. Olshevska, N. Povarova

OVERVIEW OF POPULAR APPROACHES IN CREATING CLIENT-SERVER APPLICATIONS BASED ON SCIENTOMETRICS ONAFTS’ PLATFORM

Дата

2018

Автори

D. Salskyi, A. Kozhukhar, O. Olshevska, N. Povarova

Анотація

Most of the currently developed systems are based on the client-server architecture. This architecture is usedeverywhere, from mobile-native development to Web applications.However implementing an application based on this architectural solution requires quite a lot of effort from the softwaredeveloper, and therefore, in order to simplify and speed up the development, certain standard solutions and approachesappeared. This article will discuss the most popular technologies used in the development of Web applications in the context ofenterprise development.Also in this article will be mentioned the project, built on the architecture of "client-server" - ScienceToMetrics.The main theme of this project is the study of science-metric indicators for the structural divisions of the faculty of theOdessa National Academy of Food Technologies. In fact, it is a portal for viewing and editing information on employees, inthe future this portal may be extended to subprojects.In this project, the main idea of this architecture was embodied: decomposition of the application into atomic parts inorder to distribute it to several hardware units of capacity to improve performance. The client is an independent application,which at the same time receives information from an external API-interface through REST-requests. In turn, the backendprovides this API with certain security restrictions on the content provided. The backend for this architecture provides a layerfor the content of the data users, whether it's a database (NoSQL, SQL) or an integration API with external aggregationsystems. To ensure the necessary level of security, JWT (Javascript Web Token) authorization is used, which allows you not tocreate an explicit session between the client and the backend, but allows you to communicate through a token that stores allthe necessary meta-information for this user.