\documentclass[10pt]{article}

\usepackage{fullpage}
\usepackage{setspace}
\usepackage{parskip}
\usepackage{titlesec}
\usepackage[section]{placeins}
\usepackage{xcolor}
\usepackage{breakcites}
\usepackage{lineno}
\usepackage{hyphenat}





\PassOptionsToPackage{hyphens}{url}
\usepackage[colorlinks = true,
            linkcolor = blue,
            urlcolor  = blue,
            citecolor = blue,
            anchorcolor = blue]{hyperref}
\usepackage{etoolbox}
\makeatletter
\patchcmd\@combinedblfloats{\box\@outputbox}{\unvbox\@outputbox}{}{%
  \errmessage{\noexpand\@combinedblfloats could not be patched}%
}%
\makeatother


\usepackage{natbib}




\renewenvironment{abstract}
  {{\bfseries\noindent{\abstractname}\par\nobreak}\footnotesize}
  {\bigskip}

\titlespacing{\section}{0pt}{*3}{*1}
\titlespacing{\subsection}{0pt}{*2}{*0.5}
\titlespacing{\subsubsection}{0pt}{*1.5}{0pt}


\usepackage{authblk}


\usepackage{graphicx}
\usepackage[space]{grffile}
\usepackage{latexsym}
\usepackage{textcomp}
\usepackage{longtable}
\usepackage{tabulary}
\usepackage{booktabs,array,multirow}
\usepackage{amsfonts,amsmath,amssymb}
\providecommand\citet{\cite}
\providecommand\citep{\cite}
\providecommand\citealt{\cite}
% You can conditionalize code for latexml or normal latex using this.
\newif\iflatexml\latexmlfalse
\providecommand{\tightlist}{\setlength{\itemsep}{0pt}\setlength{\parskip}{0pt}}%

\AtBeginDocument{\DeclareGraphicsExtensions{.pdf,.PDF,.eps,.EPS,.png,.PNG,.tif,.TIF,.jpg,.JPG,.jpeg,.JPEG}}

\usepackage[utf8]{inputenc}
\usepackage[english]{babel}



\usepackage{float}








\begin{document}

\title{Performance Analysis and Comparison of Node.Js and Java Spring Boot in
Implementation of Restful Applications}



\author[1]{Shyam Mohan J S}%
\author[2]{Krishanu Goswami}%
\affil[1]{GITAM - Bengaluru Campus}%
\affil[2]{Liverpool John Moores University}%


\vspace{-1em}



  
  \date{June 14, 2024}


\begingroup
\let\center\flushleft
\let\endcenter\endflushleft
\maketitle
\endgroup





\selectlanguage{english}
\begin{abstract}
The response time of a website has an impact on the overall user
experience. Slow-loading or unresponsive applications can quickly
frustrate and alienate users, leading to dissatisfaction and potentially
driving them away. Conversely, fast and efficient applications can
greatly enhance user engagement, satisfaction, and ultimately contribute
to the success of an online business. The main objective of this work is
to check and compare the performance between Node.js and Java Spring
Boot, in the context of implementing RESTful applications. REST
(Representational State Transfer) has emerged as a dominant
architectural style for building web services due to its simplicity,
scalability, and compatibility with the stateless nature of the web. To
achieve this objective, both implementations were created with an
identical business use case, aiming to provide the fundamental CRUD
operations (Create, Read, Update, and Delete). To conduct the
performance analysis, Apache JMeter tool is used that enables the
creation of a diverse set of concurrent virtual users, simulating
real-world scenarios to load both applications at regular intervals. By
subjecting the applications to varying user loads, it can be assessed
how each platform performs under different workloads and identify
potential bottlenecks and areas for improvement. The results obtained
suggest that Node.js excels in faster response times for HTTP GET, ideal
for read operations. However, Spring Boot outperforms Node.js for
complex operations like POST, PUT, and DELETE under higher user loads.
Both faced challenges at 64000 virtual users, with error rates from 10\%
to 75\%, but Spring showed better error handling. Spring required fewer
lines of code, benefiting from its environment and dependencies.
Resource utilization in Node.js proved to be efficient with CPU load
below 40\% even under heavy loads. Spring on the other hand provided
better response times, exhibited higher CPU usage at times, suggesting
more resource-intensive optimization. The comparison emphasizes the
importance of technology stack choice in development, speed and
performance. The findings serve as a basis for developers to make
informed decisions when selecting the appropriate technology stack based
on specific project requirements, workload considerations, and
performance expectations.%
\end{abstract}%



\sloppy


\textbf{Hosted file}

\verb`Wiley_SPE_2023.doc`  available at \url{https://authorea.com/users/671723/articles/671117-performance-analysis-and-comparison-of-node-js-and-java-spring-boot-in-implementation-of-restful-applications}

\selectlanguage{english}
\FloatBarrier
\end{document}

