Claim Missing Document
Check
Articles

Found 12 Documents
Search

Design and Development of a GAS-Based E-Commerce Application with UI/UX Optimization Using a User-Centered Design Approach Wahyu Nofiyan Hadi; Umi Diantika Susilowati; Anisa Nurul Wilda; Moh. Fadel; Muhammad Ichsan; Syifa Ayu Via Mika Bahrul; Rojil Ghufron; Arya Dwi Nugraha; Yoga Ari Tofan
IJCONSIST JOURNALS Vol 7 No 2 (2026): March
Publisher : International Journal of Computer, Network Security and Information System

Show Abstract | Download Original | Original Source | Check in Google Scholar | DOI: 10.33005/ijconsist.v7i2.191

Abstract

Micro, Small, and Medium Enterprises (MSMEs) offering custom embroidery and tailoring services face significant challenges with digitizing orders. Conventional e-commerce platforms primarily serve ready-made products. They lack flexibility for custom workflow options, like letting customers submit their own designs or bring in clothing for embroidery. MSMEs are often burdened by ongoing server maintenance costs. This study seeks to design and implement a web-based e-commerce information system using a User-Centered Design (UCD) approach. The case study is applied to Cindy Bordir in Probolinggo. To address the research gap regarding high-cost and rigid platforms, the application introduces a zero-cost serverless architecture. This uses Google Apps Script (GAS) and Google Spreadsheet as the database. A "Hybrid Checkout" flow bridges the digital catalog experience with localized negotiation habits via WhatsApp. Results show that applying UCD via a mobile-first interface, chip-style product variations, and micro-interaction feedback effectively support custom transaction needs. Functional testing confirmed a 100% success rate for all features. Usability evaluations using the System Usability Scale (SUS) achieved an "Excellent" score of 84.5, indicating high user satisfaction. The serverless architecture paired with the hybrid checkout approach proved to be a highly cost-effective and manageable solution for MSMEs. It eliminates traditional hosting fees while maintaining operational reliability.
Tail latency, throughput, and memory overhead of monolithic and microservices architectures in resource-constrained docker deployments Yoga Ari Tofan
JUTI: Jurnal Ilmiah Teknologi Informasi Vol. 24, No. 2, July 2026
Publisher : Institut Teknologi Sepuluh Nopember

Show Abstract | Download Original | Original Source | Check in Google Scholar | DOI: 10.12962/j24068535.v24i2.a1516

Abstract

Software architecture selection directly impacts system performance and resource efficiency. This motivates controlled comparisons to make pragmatic deployment decisions. This study compares the implementation of the same backend system, Node.js/Express and MariaDB, in a monolithic and microservices architecture with the same Docker resource allocation, 2 CPUs and 512 MB RAM per architecture, except database containers. The load test was carried out with Apache JMeter 5.6.3 with three levels of concurrency (50, 200, 500 users). Each scenario was performed 20 times within 60 s. The main metrics were response time P90, P95, throughput, error rate, CPU/RAM utilization. The monolithic implementation performed better than the microservices at all load levels. The monolith reached P90 131.35 ms and 429.89 req/s versus microservices P90 171.38 ms and 332.38 req/s at 50 users, and P90 1217.60 ms and 438.25 req/s versus 1534.50 ms and 343.24 req/s at 500 users. Statistical analysis All differences were statistically significant (Mann-Whitney U, p < 0.0001, |δ| = 1.000). For both architectures, the throughput plateaued at load levels. The most operationally significant difference in resource usage was in memory overhead at 500 users, the monolith used 95.31 ± 1.99 MiB compared to 319.43 MiB aggregate for microservices (3.35x higher). CPU utilization was broadly comparable across architectures. The results presented here are specific to this experimental configuration, i.e. a single-machine Docker deployment, two-service decomposition, and synchronous HTTP/REST communication, and should not be generalized to monolithic and microservices architectures in general.