Kamal Azizov · Zenodo (CERN European Organization for Nuclear Research) · 2026
Microservices Platform v1.0.0 This release accompanies the research paper: "Towards Low-Latency Secure Microservices: A Reactive Architecture Using JWT, mTLS, and RSocket" What's Included ✅ 4 microservices with mTLS communication ✅ Complete authentication system with JWT tokens ✅ RBAC and CBAC authorization ✅ RSocket + Protobuf communication in interservice communication ✅ Security monitoring and logging ✅ Docker Compose deployment ✅ Automated certificate generation Quick Start git clone https://github.com/Rungrukuk/Microservices-Platform.git cd Microservices-Platform ./setup.sh docker compose up --build Documentation README.md - Complete setup and API guide Architecture API Gateway: HTTPS entry point (port 8443) Auth Service: Authentication/authorization (port 7000) User Service: Domain business logic (port 7001) Monitoring Service: Event logging (port 7002) Citation If you use this project in your research, please cite: Kamal Azizov. Microservices Platform: A high-security, latency-optimized microservices architectured platform, 2026. https://github.com/Rungrukuk/Microservices-Platform.
Cited by 0Open access
Dharmendra Shadija, Mo Rezai, Richard Hill · 2017
Microservice Architectures (MA) have the potential to increase the agility of software development. In an era where businesses require software applications to evolve to support emerging software requirements, particularly for Internet of Things (IoT) applications, we examine the issue of microservice granularity and explore its effect upon application latency. Two approaches to microservice deployment are simulated; the first with microservices in a single container, and the second with microservices partitioned across separate containers. We observed a negligible increase in service latency for the multiple container deployment over a single container.
Cited by 46
Kainz, Hannes · FH CAMPUS 02 Publikationsserver · 2023
Der Fokus dieser Arbeit liegt auf dem Identifizieren und Verifizieren des Einflusses von Microservices auf die Codequalität von Softwareanwendungen. Im ersten Teil der Arbeit sind Definitionen und Architekturen der untersuchten Softwareapplikationen dargelegt. Dies beinhaltet die Definition von monolithischer Software und deren Architektur und die Definition von Microservices mit seinen Vorteilen (zum Beispiel die Skalierung durch automatisiertes Deployment) und Nachteilen (zum Beispiel höhere Komplexität durch die erhöhte Anzahl von Softwareteilen). Darauf folgt eine Analyse von den ähnlichen Softwarearchitekturkonzepten der serviceorientierten Architektur und den Self-contained Services. Der Theorieteil zu Microservices endet mit der Darstellung von Methoden zur Trennung von monolithischer Software in Microservices und wie diese Dienste wieder zu einer Gesamtanwendung zusammengeführt werden können. Zur Vervollständigung ist der aktuelle Forschungsstand auf dem Gebiet der Microservices angeführt und es wird ein Einblick in eine Auswahl an Softwaremetriken zur Erhebung von Softwarequalität gegeben. Im praktischen Teil der Arbeit wurden die theoretischen Erkenntnisse an einer Softwareapplikation angewandt. Von einem Monolithen wurden Microservices abgespalten und die resultierende Anwendung als auch der Monolith einer Softwarearchitekturanalyse unterzogen. Danach wurden Softwaremetriken für die Ausgangsapplikation und die Microservices berechnet, um festzustellen, ob sich die Codequalität verändert hat. Zum Abschluss wurde eine Analyse der Änderungsgeschwindigkeit in beiden Applikationen durchgeführt, gefolgt von Interviews mit Softwareentwicklern zu dem Qualitätsmerkmal Lesbarkeit von Quellcode. Die Ergebnisse zeigen eine Verringerung der Komplexität des entstandenen Quellcodes und eine Erhöhung der Lesbarkeit gegenüber der Ausgangsanwendung.
Cited by 0Open access
Jinmin Yang · 2025
Cited by 0
Lucas Krause · 2016
Microservices is a new trend in software development, this talk is divided into the theory of Microservices explaining the why and what of Microservices. The second part will dive into specific code building and refactoring a software application into a Microservices Architecture including refactoring, re-design, testing and security.
Cited by 3
Vaarnamo, Touko · Aaltodoc (Aalto University) · 2017
Cited by 0
Johannes Thönes · IEEE Software · 2015
In this excerpt from Software Engineering Radio, Johannes Thönes talks with James Lewis, principal consultant at ThoughtWorks, about microservices. They discuss microservices' recent popularity, architectural styles, deployment, size, technical decisions, and consumer-driven contracts. They also compare microservices to service-oriented architecture and wrap up the episode by talking about key figures in the microservice community and standing on the shoulders of giants. The Web extra at http://www.se-radio.net/2014/10/episode-213-james-lewis-on-microservices is an audio recording of Tobias Kaatz speaking with James Lewis, principal consultant at ThoughtWorks, about microservices. They discuss microservices' recent popularity, architectural styles, deployment, size, technical decisions, and consumer-driven contracts. They also compare microservices to service-oriented architecture and wrap up the episode by talking about key figures in the microservice community and standing on the shoulders of giants.
Cited by 460Open access
Jamshidi, P, Pahl, Claus, Mendonca, NC et al. · View · 2018
Cited by 0
Jamshidi, P, Pahl, Claus, Mendonca, NC et al. · View · 2018
Cited by 0
Douglas E. Comer · 2021
Cited by 1
Kamal Azizov · Zenodo (CERN European Organization for Nuclear Research) · 2026
##Reactive Microservices Platform v1.0.0 What's Included ✅ 4 microservices with mTLS communication ✅ Complete authentication system with JWT tokens ✅ RBAC and CBAC authorization ✅ RSocket + Protobuf communication in interservice communication ✅ Security monitoring and logging ✅ Docker Compose deployment ✅ Automated certificate generation Quick Start git clone https://github.com/Rungrukuk/Reactive-Microservices-Platform.git cd Microservices-Platform chmod +x setup.sh ./setup.sh docker compose up --build Documentation README.md - Complete setup and API guide
Cited by 0Open access
Sean Whitesell, Rob Richardson · Apress eBooks · 2025
In this chapter, we discuss ensuring maximum observability of microservices. OpenTelemetry has become the standard health monitoring tool, so we really lean in and look at the benefits of OpenTelemetry. .NET Aspire is a great way to easily set up OpenTelemetry and use it during local development and debugging. We can use custom logs, traces, and metrics to add additional visibility to microservices, allowing us to easily find the source of a future problem. In production, we can use Azure Application Insights to capture production logs, traces, and metrics through OpenTelemetry.
Cited by 0
Kamal Azizov · Zenodo (CERN European Organization for Nuclear Research) · 2026
##Reactive Microservices Platform v1.0.0 What's Included ✅ 4 microservices with mTLS communication ✅ Complete authentication system with JWT tokens ✅ RBAC and CBAC authorization ✅ RSocket + Protobuf communication in interservice communication ✅ Security monitoring and logging ✅ Docker Compose deployment ✅ Automated certificate generation Quick Start git clone https://github.com/Rungrukuk/Reactive-Microservices-Platform.git cd Microservices-Platform chmod +x setup.sh ./setup.sh docker compose up --build Documentation README.md - Complete setup and API guide
Cited by 0Open access
Puri, Jatin, Palanimalai, Selvam · CERN Document Server (European Organization for Nuclear Research) · 2016
Cited by 0
Petrovich, A. S. · Репозиторий БГУИР (BSUIR Repository) · 2017
Microservices are the next generation of service-oriented architecture (SOA) and they are used to create decentralized distributed software systems with low coupling and strong cohesion. The purpose of this article is to explain the main principles of MSA.
Cited by 0
Sean Whitesell, Rob Richardson · Apress eBooks · 2025
This chapter discusses containerized deployment options for .NET microservices. Though it’s possible to deploy ASP.NET to IIS, we specifically don’t discuss that here because it’s a legacy deployment system. Instead, we focus on all the places Linux containers can run in Azure, nodding to other cloud providers and other Azure container hosting platforms. We containerize a .NET app into a Docker container, run in various Azure resources that run containers, then discuss reverse proxies that allow a single URL to all the microservices.
Cited by 0
Binildas Christudas · Apress eBooks · 2019
The complexity of enterprise software systems increases with increase in the functionalities and features supported. As you saw in Chapter 1 , every enterprise system today needs to transfer information seamlessly with many other systems, both internal and external to the organization. Traditionally we have been building software systems as a “modular monolith.” By modular, we mean to say that they follow the principles of modules, layers, and tiers and hence there exists a logical modularity for elements within the software system. By monolith, we mean to say that the entire system is built with a specific scenario of deployment and operation in mind; most of the time, they are deployed as a single process or at the maximum they are distributed following the three-tier or n-tier architecture you saw in Chapter 1 . But there ends the flexibility of deployment. Equally important is the process to be followed in getting such a system built in a multiteam or a distributed team organization.
Cited by 1
Hao Xu, Terrell Russell, Jason Coposky et al. · Synthesis lectures on information concepts, retrieval, and services · 2017
Cited by 0
Sean Whitesell, Rob Richardson · Apress eBooks · 2025
Twitter, PayPal, and Netflix had serious problems. Problems like scaling, quality, and downtime became common and increasing issues. Each had a large, single-code base application known as a “monolith.” And each hit different frustration points where a fundamental architecture change had to occur. Development and deployment cycles were long and tedious, causing delays in feature delivery. Each deployment meant downtime or expensive infrastructure to switch from one set of servers to another. As the code base grew, so did the coupling between modules. With coupled modules, code changes are more problematic, harder to test, and lower overall application quality.
Cited by 0
Garofolo, Ethan · CERN Document Server (European Organization for Nuclear Research) · 2020
Cited by 0