Fig 2 - uploaded by Indika Perera
Content may be subject to copyright.
High-level architecture design diagram for Commission Calculator. details are two system requirements for the Commission Calculator system which are categorized under finance feature category and only consumed by the desktop client).
Source publication
Software is ubiquitous in today’s systems and
business operations. Most importantly the architecture of a
software system determines its quality and longevity, because
the development work related to the software system will be
carried out to be in line with its architecture design. Hence, it’s
highly important to structure the high-level software...
Contexts in source publication
Context 1
... PROPOSED TECHNIQUE TheArchitect, consisting of a modularized architecture as illustrated in Fig. 1 automates the generation of serverless- microservices based high-level architecture as shown for Com- mission Calculator system in Fig. ...
Context 2
... module will display the generated high-level archi- tecture design by depicting as labeled components and in- teractions among them as shown for Commission Calculator system in Fig. 2. Commission Calculator is a system which allows merchant assistants to calculate their commission for a particular sale. This system contains both a desktop and a mobile client in which both clients are equipped with similar behaviour in terms of log in, setting profile preferences and calculating commission. Only the desktop client ...
Context 3
... of architecture generation algorithm and visual representation module will be discussed in detail with respect to automating the serverless-microservices based high- level architecture for the Commission Calculator application shown in Fig. 2 and the serverless technology analysis shown in Fig. 3. ...
Context 4
... high-level architecture is visually represented using named components along with their interactions among each other using Fabric.js library [25] as shown in Fig. 2. This will iterate through each path model within the paths list returned from Algorithm 1. The list will contain one path model per each user provided feature category, which will result in drawing a complete path for each feature category. Firstly, visual representation technique will identify the number of application clients the ...
Citations
... In contrast, an IBM team examined how different architectures utilize resources under various operational settings and hardware configurations, and discovered that monolithic apps typically outperformed microservices, contradicting Singh and Peddoju's findings. [5] This contradiction merits more consideration in this study. Furthermore, Mark Richards examines these notions by comparing microservices to Service Oriented Architectures in his publications. ...
software development and deployment by increasing modularity, scalability, and flexibility. This technique divides apps into smaller, independent services that communicate over HTTP APIs. Docker plays an important role in containerizing these services, guaranteeing consistent operation across several settings. Docker containers are lightweight, use the host kernel, and start quicker than typical virtual machines, making them perfect for microservices. Kubernetes, Google's open-source technology, enhances microservices by automating container deployment, scaling, and administration across host clusters. This combination creates a stable environment for delivering microservices, allowing for continuous integration and deployment (CI/CD). This article investigates the synergistic usage of microservices, Docker, and Kubernetes, showing their combined efficiency in developing, deploying, and scaling applications across many environments. Keywords— microservice, architecture, Monolithic Architecture, Kubernetes, Docker
... They present a serverless abstraction that enables the seamless and scale-out features provided by current serverless architectures while supporting a wide variety of application types in a model that programmers are familiar with the same abstraction provided by an operating system today. Perera and Perera (Perera & Perera, 2018) presented TheArchitect model, which focuses on generating best fitted microservices and serverless based high-level architecture. They demonstrated a performance evaluation of TheArchitect in terms of the processing time. ...
With the increasing adoption of serverless computing, there is a need for a benchmark. The aim of this paper is to present such a benchmark based on performance and usability testing to better understand serverless services as well as help practitioners to select between two major clouds, namely, Amazon and Azure. Jmeter tool and system usability scale are used to conduct performance and usability testing, respectively. In addition, a replication package is provided to increase the validity and reliability of the results. The main findings revealed that the serverless platforms are different in their architecture. Even though both of them support the same serverless concept, they differ considerably in structure, development, and creations of services. Overall, both the cloud vendors under study provide the same core capabilities one would expect but, there are some differences too. In particular, usability could be improved to extend the market and capture more customers.
