Melola Discovery

← Melola Discovery

Open access Jurnal SINTA 1

Architectural trade-offs: comparative analysis across K3s, serverless, and traditional server deployments

International Journal of Electrical and Computer Engineering (IJECE) · Vol. 16 No. 2 (2026)

DOI
10.11591/ijece.v16i2.pp873-882
ISSN
2722-2578, 2088-8708
Published
2026-04-01
Publisher
Institute of Advanced Engineering and Science
License
creativecommons.org/licenses/by-sa/4.0

Abstract

In modern software architecture, combining serverless computing, microservices, and containers improves scalability, performance, observability, and resilience. However, choosing the right deployment strategy is crucial. Current individual deployment methods often limit productivity because of poor integration options. This study looks at three deployment approaches: Kubernetes cluster, AWS Lambda (serverless), and Traditional Java Server. We tested performance under different workloads using virtual machines and simulations. The results show that the K3s cluster provides high throughput and low latency because it manages resources directly. AWS Lambda’s pay-as-you-go model, along with its built-in cost optimization, works well for event-driven workloads. In contrast, Java Microservice is cost-effective but needs manual tuning to control latency and error rates. Bringing these scenarios together into a single service mesh architecture could help optimize costs, performance, and system resilience.

Collaboration network of the authors

8 authors · 28 co-authorship links

Hover or tap a name to highlight its co-authors. Double-click to open the author's page.

  • R.V. College of Engineering
  • Different organisations
  • Same organisation
  • Affiliation unknown
  • Thicker line = more joint articles · bigger circle = more articles
Show as table
Co-authorOrganisationJoint articles

Affiliations come from OpenAlex; journal OAI-PMH metadata carries none. Authors without an OpenAlex ID are matched by name, which can merge or split people.

This record comes from Crossref (what the publisher deposited), because the journal's own OAI-PMH endpoint could not be harvested.

Metadata source: Crossref API (cadangan, berdasarkan ISSN) https://api.crossref.org/journals/2088-8708/works, first harvested 27 Okt 2026, last seen 27 Okt 2026.
Metadata as oai_dc, converted from Crossref
<oai_dc:dc xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"><dc:title>Architectural trade-offs: comparative analysis across K3s, serverless, and traditional server deployments</dc:title><dc:creator>P., Prajwal</dc:creator><dc:creator>Teli, Naveen B.</dc:creator><dc:creator>H. N., Nishal</dc:creator><dc:creator>Dey, Nimisha</dc:creator><dc:creator>Deenadhayalan, Pratiba</dc:creator><dc:creator>Pattar, Ramakanth Kumar</dc:creator><dc:creator>Hadagali, Pavithra</dc:creator><dc:creator>P. R., Skanda</dc:creator><dc:description>&lt;jats:p&gt;In modern software architecture, combining serverless computing, microservices, and containers improves scalability, performance, observability, and resilience. However, choosing the right deployment strategy is crucial. Current individual deployment methods often limit productivity because of poor integration options. This study looks at three deployment approaches: Kubernetes cluster, AWS Lambda (serverless), and Traditional Java Server. We tested performance under different workloads using virtual machines and simulations. The results show that the K3s cluster provides high throughput and low latency because it manages resources directly. AWS Lambda’s pay-as-you-go model, along with its built-in cost optimization, works well for event-driven workloads. In contrast, Java Microservice is cost-effective but needs manual tuning to control latency and error rates. Bringing these scenarios together into a single service mesh architecture could help optimize costs, performance, and system resilience.&lt;/jats:p&gt;</dc:description><dc:publisher>Institute of Advanced Engineering and Science</dc:publisher><dc:date>2026-04-01</dc:date><dc:type>info:eu-repo/semantics/article</dc:type><dc:format>application/pdf</dc:format><dc:identifier>https://doi.org/10.11591/ijece.v16i2.pp873-882</dc:identifier><dc:identifier>10.11591/ijece.v16i2.pp873-882</dc:identifier><dc:source>International Journal of Electrical and Computer Engineering (IJECE); Vol 16 No 2 (2026); 873</dc:source><dc:source>2722-2578</dc:source><dc:source>2088-8708</dc:source><dc:relation>https://ijece.iaescore.com/index.php/IJECE/article/viewFile/40142/18692</dc:relation><dc:rights>http://creativecommons.org/licenses/by-sa/4.0</dc:rights></oai_dc:dc>