2026· International Journal of Artificial Intelligence & Digital Transformation· 1 citation
TL;DR
This paper explores the integration of Spring Boot with containerization and observability, focusing on best practices, architectural patterns, and challenges, and delves into containerization strategies using Docker and orchestration with Kubernetes, emphasizing their roles in deployment and scalability.
Abstract
Microservices architecture has revolutionized software development by promoting scalable, flexible, and maintainable systems through the decomposition of applications into independent, loosely coupled services. When combined with Spring Boot, containerization technologies like Docker, and observability practices, organizations can build robust applications that are both efficient and resilient. This paper explores the integration of Spring Boot with containerization and observability, focusing on best practices, architectural patterns, and challenges. It delves into containerization strategies using Docker and orchestration with Kubernetes, emphasizing their roles in deployment and scalability. The importance of observability is highlighted through logging, monitoring, and distributed tracing, alongside the implementation of Continuous Integration and Continuous Deployment (CI/CD) pipelines for automated deployment. Additionally, the paper addresses critical security considerations in microservices architectures, providing real-world examples and data to illustrate the effectiveness of various practices and technologies.
Cloud-native architecture has been the new paradigm in enterprise application development that facilitates organization to reach unprecedented levels of scalability, agility, reliability, and operational efficiency. The dynamic business requirements, short delivery cycles of software solutions and the necessity of globally distributed services are mounting an increasing challenge on traditional monolithic systems. The concepts of microservices architecture, containerization, DevOps culture, and continuous delivery pipelines are the main principles in cloud-native systems that circumvent the limitations. This paper will be a detailed study of cloud-native architecture and its strategic role in a digital transformation process of businesses. Scalability models, distributed resource management, service orchestration, elasticity patterns and resilience techniques applied by cloud-native platforms are further detailed in the abstract. We address the transformation of enterprise application infrastructure out of on-premise legacy resource setting into service-based cloud environments properly configured to scale horizontally. The paper also investigates that the container orchestration systems such as Kubernetes make deployment, scaling, and failover operations to be declaratively automated. The purpose of service mesh, API-oriented architecture, event-based systems, policy-oriented autoscaling, and infrastructure-as-code (IaC) are examined to show how the architectural resilience and operational administration are accomplished. An approach to assess the maturity of cloud-native systems is presented based on the performance benchmarking, lifecycle automation, security compliance, and cost optimization indicators as part of a methodological framework. Also, the paper presents experimental evaluations of the response time, throughput, service resiliency, and infrastructure utilization in both traditional and cloud-native deployments. Findings indicate the application availability, frequency of deployment and scalability efficiency are very high. Lastly, such challenges as state management, data consistency, complexities in migrating, observability, and operational complexity are also addressed. The innovations that are emphasized by the best practices and future-oriented thinking include serverlesscomputing, auto-scaling that is run with AI, workloads based on WebAssembly, and automated cloud operations. All in all, the paper points to the idea that cloud-native architectures are not something the enterprises can afford to ignore on their quest towards maintaining competitive viability in the rapidly changing digital economy.
Kanya Mohammed, Naree Thongchai· International Journal of Mod...· 0 citations
The article examines a coherent set of principles for constructing observability systems in cloud-based applications, employing the OpenTelemetry standard as a primary instrument for achieving transparency, predictability, and controllability across distributed computing environments. The relevance of the study is conditioned by the rapid proliferation of cloud-native architectures and the need for unified mechanisms to correlate metrics, traces, and logs within multiservice, elastically scalable systems. The objective is to identify and systematize architectural and methodological principles that enable the design of observable applications grounded in the OTLP (OpenTelemetry Protocol) unified protocol and OpenTelemetry’s native integration into the Microsoft ecosystem. The novelty lies in a holistic treatment of observability not as an isolated technical module but as an embedded engineering discipline spanning the entire application life cycle, from project templates and CI/CD pipelines to cloud operations. The article proposes viewing OTLP as a telemetry USB port for distributed systems, enabling signal portability across monitoring platforms (Grafana, Azure, Dynatrace) without code changes or violating architectural invariants. Key results include substantiating OpenTelemetry’s role as a lingua franca between applications and analytics platforms; distinguishing three principal telemetry-collection topologies (sidecar, gateway, and managed); and analyzing their trade-offs between contextual proximity and operational overhead. The article is intended for DevOps engineers, cloud solution architects, developers, and researchers in telemetry and cloud-native technologies seeking to build a predictable, interpretable, and scalable observability system.
S. Yakhin· Journal of Electrical System...· 0 citations
This paper analyzes the two software architectural approaches namely Monolithic Architecture vs Microservices Architecture when considering scalable software development, and puts the following into consideration: empirical trade-offs, scalability consideration, organizational implications, and development complexity.
Theophilus Bamise Ajala, A. Oduroye, I. Ayoade et al.· Asian journal of applied sci...· 0 citations
Results indicate that organizations adopting microservices design on Kubernetes can achieve higher deployment frequency, better resiliency, improved resource utilization and greater agility to respond to evolving market needs.
Srichandra Boosa· American International Journ...· 0 citations
This paper presents a systematic, practice-driven evaluation of WebAssembly (WASM) as an execution substrate for cloud-native workloads orchestrated through Docker and Kubernetes using runwasi. We develop a reproducible workflow that compiles Rust and Go/TinyGo applications to WASM modules, applies Ahead-of-Time (AOT) optimizations per engine and architecture, and packages minimal OCI artifacts for multi-architecture deployment (amd64, arm64, riscv64). Through controlled experiments on heterogeneous nodes, we benchmark eight CPU-bound workloads, reporting mean, median, and confidence intervals to ensure statistical robustness. The results show that WASM achieves latencies close to native on amd64/arm64, with WasmEdge leading under AOT and Wasmtime offering strong compatibility and stability. Artifact sizes are substantially smaller than traditional containers, improving pull times and packing density. While riscv64 execution is feasible, it remains less mature and more sensitive to engine and build choices. Overall, the findings demonstrate that WASM is a viable and efficient option for Cloud Continuum environments when deployments rely on AOT-optimized artifacts, RuntimeClass-based scheduling, and workloads aligned with the WASI feature set supported by the selected engines.
Álvaro Vázquez-Rodríguez, David Vila-Pérez, Carlos Giraldo-Rodíguez et al.· International Conference on...· 0 citations
Internal Developer Platforms built on Kubernetes mark a significant change in how enterprises deliver software. Platform engineering teams create self-service environments that hide the complexity of infrastructure, allowing application developers to set up, deploy, and manage containerised applications without needing extensive knowledge of Kubernetes. This discipline uses standard templates, automated pipelines, and governance controls based on cloud-native features like Custom Resource Definitions, Helm charts, and role-based access control. These platforms rely on microservice architectures, which offer independently deployable services that interact through well-defined application programming interfaces. At the datacentre level, multi-path networking and bonding strategies ensure high availability, directly supporting service level agreements that require almost constant uptime. GitOps continuous delivery methods, using tools like Argo CD, make Git repositories the main source of truth for both application settings and cluster status, removing the need for manual deployment tasks and preventing configuration inconsistencies. Platform engineering teams in sectors such as hospitality, retail, and media gain clear business agility, faster deployment times, and long-term service reliability through this integrated approach.
S. Kanchumarthi· World Journal of Advanced Re...· 0 citations