Relevant bibliographies by topics / Microservices

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Books
  4. Book chapters
  5. Conference papers
  6. Reports

Academic literature on the topic 'Microservices'

Author: Grafiati
Published: 4 June 2021
Last updated: 8 June 2024

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Microservices.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "Microservices"

1

Park, Joonseok, Daeho Kim, and Keunhyuk Yeom. "An Approach for Reconstructing Applications to Develop Container-Based Microservices." Mobile Information Systems 2020 (January 29, 2020): 1–23. http://dx.doi.org/10.1155/2020/4295937.

Full text
Abstract:
Microservices are small-scale services that can operate independently. An application consisting of microservice units can be developed independently as a service unit, and it can handle individual logic without being affected by other services. In addition, it is possible to rapidly distribute the configured microservices by a container, and a container orchestration technology that manages the distributed multiple containers can be realized; thus, it is possible to update and distribute the microservices separately. Therefore, many companies are moving away from existing monolithic structures and attempting to switch to microservices. In this paper, we present a method for reconstructing a monolithic application into a container-based microservice unit. The microservices of data units are derived through the collection and analysis of monolithic design data. Furthermore, we propose a method to generate a template script based on deployment design data so that the derived microservice and support distribution can be implemented in a container environment. The results of a case study conducted verified that the container-based microservices deployed in this study work properly. In addition, for the development of monolithic applications and the development of container-based microservices presented in this paper, we confirmed that developing on the basis of microservices is efficient by conducting execution time performance evaluation for API calls at various iterations. Finally, we show that microservices constructed using the proposed method have higher reusability than those constructed using existing methods.
APA, Harvard, Vancouver, ISO, and other styles
2

Li, David Chunhu, Chiing-Ting Huang, Chia-Wei Tseng, and Li-Der Chou. "Fuzzy-Based Microservice Resource Management Platform for Edge Computing in the Internet of Things." Sensors 21, no. 11 (May 31, 2021): 3800. http://dx.doi.org/10.3390/s21113800.

Full text
Abstract:
Edge computing exhibits the advantages of real-time operation, low latency, and low network cost. It has become a key technology for realizing smart Internet of Things applications. Microservices are being used by an increasing number of edge computing networks because of their sufficiently small code, reduced program complexity, and flexible deployment. However, edge computing has more limited resources than cloud computing, and thus edge computing networks have higher requirements for the overall resource scheduling of running microservices. Accordingly, the resource management of microservice applications in edge computing networks is a crucial issue. In this study, we developed and implemented a microservice resource management platform for edge computing networks. We designed a fuzzy-based microservice computing resource scaling (FMCRS) algorithm that can dynamically control the resource expansion scale of microservices. We proposed and implemented two microservice resource expansion methods based on the resource usage of edge network computing nodes. We conducted the experimental analysis in six scenarios and the experimental results proved that the designed microservice resource management platform can reduce the response time for microservice resource adjustments and dynamically expand microservices horizontally and vertically. Compared with other state-of-the-art microservice resource management methods, FMCRS can reduce sudden surges in overall network resource allocation, and thus, it is more suitable for the edge computing microservice management environment.
APA, Harvard, Vancouver, ISO, and other styles
3

Jhingran, Sushant, and Nitin Rakesh. "Performance Analysis of Microservices Behavior in Cloud vs Containerized Domain based on CPU Utilization." International Journal on Recent and Innovation Trends in Computing and Communication 11, no. 6s (June 13, 2023): 509–16. http://dx.doi.org/10.17762/ijritcc.v11i6s.6959.

Full text
Abstract:
Enterprise application development is rapidly moving towards a microservices-based approach. Microservices development makes application deployment more reliable and responsive based on their architecture and the way of deployment. Still, the performance of microservices is different in all environments based on resources provided by the respective cloud and services provided in the backend such as auto-scaling, load balancer, and multiple monitoring parameters. So, it is strenuous to identify Scaling and monitoring of microservice-based applications are quick as compared to monolithic applications [1]. In this paper, we deployed microservice applications in cloud and containerized environments to analyze their CPU utilization over multiple network input requests. Monolithic applications are tightly coupled while microservices applications are loosely coupled which help the API gateway to easily interact with each service module. With reference to monitoring parameters, CPU utilization is 23 percent in cloud environment. Additionally, we deployed the equivalent microservice in a containerized environment with extended resources to minimize CPU utilization to 17 percent. Furthermore, we have shown the performance of the application with “Network IN” and “Network Out” requests.
APA, Harvard, Vancouver, ISO, and other styles
4

Karlingannavar, Rakshata, and Dr Nagaraj Bhat. "Orchestration of Micro services Using Conductor." Journal of University of Shanghai for Science and Technology 23, no. 06 (June 4, 2021): 250–55. http://dx.doi.org/10.51201/jusst/21/05254.

Full text
Abstract:
The Microservices architectural design is widely used today which helps one to build an application as a set of services that can be developed and deployed independently. Each service is independent and gives a set of functions or features that can be individually serviced. In spite of the fact that microservices design has been advanced as the fix just for all cutting-edge application development ailments and is viewed as the replacement for API first application advancement, its execution needs undeniably more idea and practicality. In order for these independent services to work together towards a common goal, we need something that will stitch them together because they cannot work in complete isolation and need to share data and interact with one another. There are two ways to do this – microservice choreography and microservice orchestration. This paper tries to explain the difference between choreography and orchestration of microservices, and why the latter is better. We will then discuss the orchestration of microservices using an open-sourced microservices orchestrator – Conductor.
APA, Harvard, Vancouver, ISO, and other styles
5

Pimparkhede, Kunal. "Client side and Server Side Load Balancing." International Journal for Research in Applied Science and Engineering Technology 9, no. 11 (November 30, 2021): 30–31. http://dx.doi.org/10.22214/ijraset.2021.38748.

Full text
Abstract:
Abstract: In the microservice architecture it is vital to distribute loads across replicated instances of microservices. Load distribution such that no single instance is overloaded is called as load balancing. Often the instances of microservices are replicated across different racks, different data centers or even different geographies. Modern cloud based platforms offer deployment of microservices across different server instances which are geographically disperse. Having a system that will balance the load across service instances becomes a key success criteria for accurate functioning of distributed software architecture Keywords: Load Balancing, Microservices, Distributed software system
APA, Harvard, Vancouver, ISO, and other styles
6

Shamsuddeen Rabiu, Abubakar Abba, and Mustapha Ahmed Abubakar. "Autonomous workload distribution for container-based micro services environments." World Journal of Advanced Engineering Technology and Sciences 9, no. 2 (August 30, 2023): 242–50. http://dx.doi.org/10.30574/wjaets.2023.9.2.0226.

Full text
Abstract:
Microservice architecture represents a cloud application design approach that transfers the intricacies from the conventional monolithic applications to the infrastructure. It involves breaking down the application into small, containerized microservices, each responsible for a specific functional requirement. These microservices can be independently deployed, scaled, and tested through automated orchestration systems. Our paper introduces an autonomous system for distributing workloads among containerized microservices within the cloud like a swarm, designed specifically for microservices operating within OpenVZ containers. This system has the potential to enhance performance compared to existing centralized container orchestration systems.
APA, Harvard, Vancouver, ISO, and other styles
7

Vera-Rivera, Fredy H., Carlos Gaona, and Hernán Astudillo. "Defining and measuring microservice granularity—a literature overview." PeerJ Computer Science 7 (September 8, 2021): e695. http://dx.doi.org/10.7717/peerj-cs.695.

Full text
Abstract:
Background Microservices are an architectural approach of growing use, and the optimal granularity of a microservice directly affects the application’s quality attributes and usage of computational resources. Determining microservice granularity is an open research topic. Methodology We conducted a systematic literature review to analyze literature that addresses the definition of microservice granularity. We searched in IEEE Xplore, ACM Digital Library and Scopus. The research questions were: Which approaches have been proposed to define microservice granularity and determine the microservices’ size? Which metrics are used to evaluate microservice granularity? Which quality attributes are addressed when researching microservice granularity? Results We found 326 papers and selected 29 after applying inclusion and exclusion criteria. The quality attributes most often addressed are runtime properties (e.g., scalability and performance), not development properties (e.g., maintainability). Most proposed metrics were about the product, both static (coupling, cohesion, complexity, source code) and runtime (performance, and usage of computational resources), and a few were about the development team and process. The most used techniques for defining microservices granularity were machine learning (clustering), semantic similarity, genetic programming, and domain engineering. Most papers were concerned with migration from monoliths to microservices; and a few addressed green-field development, but none address improvement of granularity in existing microservice-based systems. Conclusions Methodologically speaking, microservice granularity research is at a Wild West stage: no standard definition, no clear development—operation trade-offs, and scarce conceptual reuse (e.g., few methods seem applicable or replicable in projects other than their initial proposal). These gaps in granularity research offer clear options to investigate on continuous improvement of the development and operation of microservice-based systems.
APA, Harvard, Vancouver, ISO, and other styles
8

Mugeraya, Sanath, and Kailas Devadkar. "Dynamic Task Scheduling and Resource Allocation for Microservices in Cloud." Journal of Physics: Conference Series 2325, no. 1 (August 1, 2022): 012052. http://dx.doi.org/10.1088/1742-6596/2325/1/012052.

Full text
Abstract:
Abstract With the emergence of new companies and the expansion of the information technology sector, the need for Cloud Computing becomes apparent. Currently, the enterprises are rapidly transitioning from monolithic architecture to microservice-driven architecture. This research study has discovered that all task scheduling algorithms were designed for a specific (set) number of virtual machines, which resulted in the bottleneck problem, where multiple tasks were assigned to the microservice scheduler and the execution time of processing the tasks was significantly increased. Therefore, to address this issue, a novel model was designed based on the number of tasks and accordingly the number of virtual machines were dynamically generated to send the tasks to the microservice scheduler one by one, and the difficulties with execution time were also addressed. The study also discovered that due to the multiple workloads on the microservices, resource allocation becomes extremely difficult. To address this issue, containerized microservices were discovered. Here, the microservices would be distributed in containers. To implement the dynamic work scheduling technique, a cloud microservice translator would be developed, where a user may upload a text file and quickly get it dynamically translated. The main aim of this research work is to improve the task scheduling and resource allocation in microservices.
APA, Harvard, Vancouver, ISO, and other styles
9

Nadaf, Sarah R., and H. K. Krishnappa. "Kubernetes in Microservices." International Journal of Advanced Science and Computer Applications 2, no. 1 (November 12, 2022): 7–18. http://dx.doi.org/10.47679/ijasca.v2i1.19.

Full text
Abstract:
The move towards the microservice grounded armature is well underway. In this architectural style, small and approximately coupled modules are developed, stationed, and gauged singly to compose pall-native operations. still, for carrier- grade service providers to resettle to the microservices architectural style, vacuity remains a concern. Kubernetes is an open source platform that defines a set of structure blocks which inclusively give mechanisms for planting, maintaining, spanning, and healing containerized microservices. therefore, Kubernetes hides the complexity of microservice unity while managing their vacuity. In this paper, we probe further infrastructures and conduct further trials to estimate the vacuity that Kubernetes delivers for its managed microservices. We present different infrastructures for public and private shadows. We estimate the vacuity attainable through the mending capability of Kubernetes. We probe the impact of adding redundancy on the vacuity of microservice grounded operations. We conduct trials under the dereliction configuration of Kubernetes as well as under its most responsive bone . We also perform a relative evaluation with the Vacuity operation Framework( AMF), which is a proven result as a middleware service for managing high- vacuity. The results of our examinations show that in certain cases, the service outage for operations managed with Kubernetes is significantly high
APA, Harvard, Vancouver, ISO, and other styles
10

Laigner, Rodrigo, Yongluan Zhou, Marcos Antonio Vaz Salles, Yijian Liu, and Marcos Kalinowski. "Data management in microservices." Proceedings of the VLDB Endowment 14, no. 13 (September 2021): 3348–61. http://dx.doi.org/10.14778/3484224.3484232.

Full text
Abstract:
Microservices have become a popular architectural style for data-driven applications, given their ability to functionally decompose an application into small and autonomous services to achieve scalability, strong isolation, and specialization of database systems to the workloads and data formats of each service. Despite the accelerating industrial adoption of this architectural style, an investigation of the state of the practice and challenges practitioners face regarding data management in microservices is lacking. To bridge this gap, we conducted a systematic literature review of representative articles reporting the adoption of microservices, we analyzed a set of popular open-source microservice applications, and we conducted an online survey to cross-validate the findings of the previous steps with the perceptions and experiences of over 120 experienced practitioners and researchers. Through this process, we were able to categorize the state of practice of data management in microservices and observe several foundational challenges that cannot be solved by software engineering practices alone, but rather require system-level support to alleviate the burden imposed on practitioners. We discuss the shortcomings of state-of-the-art database systems regarding microservices and we conclude by devising a set of features for microservice-oriented database systems.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Microservices"

1

Romin, Philip. "Unraveling Microservices : A study on microservices and its complexity." Thesis, KTH, Skolan för elektroteknik och datavetenskap (EECS), 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-290292.

Full text
Abstract:
Microservices is one of the most commonly used buzzword of the systems architecture industry and is being adopted by several of the world’s largest technology companies such as Netflix, Uber and Amazon. The architecture which embraces splitting up your system in smaller independent units is an extension of the service-oriented architecture and an opponent of the monolithic architecture. Being a top buzzword and promises of extreme scalability has spiked the interest for microservices, but unlike the relatively simple monolithic architecture the complexity of microservices creates a new set of obstacles. This work sheds a light on these issues and implements solutions for some of the most frequent problems using a case study. The study shows that while microservices can help reduce the inner complexity of a system, it greatly increases the outer complexity and creates the need for a variety of tools aimed at distributed systems. It also concludes that communication and data storage are two of the most frequently occurring issues when developing microservices with the most difficult one being how you reason with and structure your data, especially for efficient queries across microservices.
Microservices eller så kallade mikrotjänster är ett ofta förekommande buzzword inom systemarkitektur och nyttjas av flera teknikjättar som exempelvis Netflix, Uber och Amazon. Arkitekturen som bygger på att dela upp sina system i mindre oberoende delar är en utbyggnad av den tjänstorienterade arkitekturen och numera motståndare till den klassiska monolitiska arkitekturen. En plats högt upp på trendlistan och lovord om extrem skalbarhet har gjort att intresset för mikrotjänster är enormt, men till skillnad från den relativt simpla monolitiska arkitekturen skapar komplexiteten hos mikrostjänster en rad nya hinder. Det här arbetet belyser dessa hinder och implementerar även lösningar för de vanligaste förekommande problemen med hjälp av en fallstudie. Resultatet visar att även fast en mikrotjänstarkitektur kan minska systemets interna komplexitet så leder det till en markant ökning av systemets yttre komplexitet och det skapas ytterligare behov av en mängd olika verktyg och tjänster designade för distribuerade system. Studien visar också att de två mest förekommande problemen vid utveckling av en mikrotjänstarkitektur är kommunikation och datalagring där hantering och struktur av data är den mest komplicerade och kräver mycket kunskap, speciellt för att skapa effektiva datasökningar som sträcker sig över flera mikrotjänster.
APA, Harvard, Vancouver, ISO, and other styles
2

Muresu, Daniel. "Investigating the security of a microservices architecture : A case study on microservice and Kubernetes Security." Thesis, KTH, Skolan för elektroteknik och datavetenskap (EECS), 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-302579.

Full text
Abstract:
The concept of breaking down a bigger application into smaller components is not a new idea, but it has been more commonly adopted in recent years due to the rise of the microservice application architecture. What has not been elaborated on enough however, is the security of the microservice architecture and how it differs from a monolithic application architecture. This leads to question what the most relevant security vulnerabilities of integrating and using a microservice architecture are, and what the correlating metrics that can be used to detect intrusions based on the vulnerabilities can be. In this report, the security of the microservice architecture is elaborated on in a case study of the system at Skatteverket, the Swedish tax agency, which is a microservice based architecture running on Kubernetes. Interviews are conducted with people that have experience in Kubernetes and microservices separately, both employed at Skatteverket and elsewhere. In the interviews, vulnerabilities and intrusion detection metrics are identified, which are then analyzed with respect to a use case in the Skatteverket system. A survey is also done on the existing technologies that can mitigate the identified vulnerabilities that are related to a microservice architecture. The vulnerabilities present in the use case are then concluded to be most relevant, the identified intrusion detection metrics are elaborated on and the service mesh technology Istio is found to mitigate largest number of the identified vulnerabilities.
Konceptet att bryta ner en större applikation i mindre komponenter är inte en ny idé, men den har blivit vanligare under de senaste åren på grund av växten i användning av mikrotjänstsarkitekturer. Vad som dock inte har utforskats tillräckligt är säkerheten för mikrotjänstarkitekturen och hur den skiljer sig från en monolitisk applikationsarkitektur. Detta leder till att fråga vilka de mest relevanta säkerhetsriskerna med att integrera och använda en mikrotjänstarkitektur är, och vilka mätvärden som kan användas för att upptäcka intrång baserat på riskerna kan vara. I denna rapport utforskas säkerheten för mikrotjänstarkitekturer genom en fallstudie av systemet hos Skatteverket, som är en mikrotjänstbaserad arkitektur som körs på Kubernetes. Intervjuer genomförs med personer som har erfarenhet av Kubernetes och mikrotjänster separat, både med anställda på Skatteverket och på annat håll. I intervjuerna identifieras risker och mätvärden för att märka av intrång som sedan analyseras med avseende på ett användningsfall i Skatteverketssystemet. En undersökning görs också om befintlig teknik som kan mildra de identifierade riskerna som är relaterade till en mikrotjänstarkitektur. De risker som förekommer i användningsfallet anses sedan till att vara mest relevanta i slutsatserna, de identifierade mätvärdena för att märka av intrång diskuteras och service mesh teknologin Istio anses mitigera störst antal av de identifierade riskerna.
APA, Harvard, Vancouver, ISO, and other styles
3

Markfjärd, Gabriel. "SLA-Aware Microservice Orchestration : Investigating How to Include SLA Resilience When Updating and Scaling Microservices." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-177704.

Full text
Abstract:
The standard functions found in Kubernetes do not allow for easy management of SLAs. Previous works have touched upon this topic in papers where aware scalers and SLA aware rollout strategies have been investigated. Neither of the relevant papers investigate the use of SLA Aware autoscalers and rollout strategies together. A motivation for investigating this combined approach is the ability to automatically rollout a new update that performs worse than the current version, but where the autoscaler could mitigate this difference and allow the new update to be deployed. This thesis utilizes the Kubernetes operator pattern to implement two operators running in the Kubernetes cluster, one taking care of autoscaling and the other taking care of rollouts. These operators were then evaluated against an SLA specifying that the rate of requests handled per second (requests/s) is important and should be at a level of at least 70. The autoscaler implemented a simple control loop, pulling metrics from the monitoring system, and comparing with the specified SLA, in order to adjust the amount of replicas the current deployment is running, based on the gap to the targeted SLA. The rollout operator utilizes the same metrics to assess the performance of the new update. The rollout strategy is a canary strategy where the new update receives an increasing amount of traffic, and on each new traffic increase the update is evaluated regarding its performance compared to the SLA. As a conclusion the thesis found that the operators combined allowed for a worse performing update to be rolled out using the rollout operator together with scaling by the autoscaler. This yielded better adherence to the SLA than the evaluated equivalent default functions Kubernetes.
APA, Harvard, Vancouver, ISO, and other styles
4

Remeika, Mantas, and Jovydas Urbanavicius. "Microservices in data intensive applications." Thesis, Linnéuniversitetet, Institutionen för datavetenskap och medieteknik (DM), 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-88822.

Full text
Abstract:
The volumes of data which Big Data applications have to process are constantly increasing. This requires for the development of highly scalable systems. Microservices is considered as one of the solutions to deal with the scalability problem. However, the literature on practices for building scalable data-intensive systems is still lacking. This thesis aims to investigate and present the benefits and drawbacks of using microservices architecture in big data systems. Moreover, it presents other practices used to increase scalability. It includes containerization, shared-nothing architecture, data sharding, load balancing, clustering, and stateless design. Finally, an experiment comparing the performance of a monolithic application and a microservices-based application was performed. The results show that with increasing amount of load microservices perform better than the monolith. However, to cope with the constantly increasing amount of data, additional techniques should be used together with microservices.
APA, Harvard, Vancouver, ISO, and other styles
5

Ericson, Amanda. "Mitigating garbage collection in Java microservices : How garbage collection affects Java microservices andhow it can be handled." Thesis, Mittuniversitetet, Institutionen för informationssystem och –teknologi, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:miun:diva-42299.

Full text
Abstract:
Java is one of the more recent programming languages that in runtime free applications from manual memory management by using automatic Garbage collector (GC) threads. Although, at the cost of stop-the-world pauses that pauses the whole application. Since the initial GC algorithms new collectors has been developed to improve the performance of Java applications. Still, memory related errors occurs and developers struggle to pick the correct GC for each specific case. Since the concept of microservices were established the benefits of using it over a monolith system has been brought to attention but there are still problems to solve, some associated to garbage collectors. In this study the performance of garbage collectors are evaluated and compared in a microservice environment. The measurements were conducted in a Java SpringBoot application using Docker and a docker compose file to simulate a microservice environment. The application outputted log files that were parsed into reports which were used as a basis for the analysis. The tests were conducted both with and without a database connection. Final evaluations show that one GC does not fit all application environments. ZGC and Shenandoah GC was proven to perform very good regarding lowering latency, although not being able to handle the a microservice environment as good as CMS. ZGC were not able to handle the database connection tests at all while CMS performed unexpectedly well. Finally, the study enlightens the importance of balancing between memory and hardware usage when choosing what GC to use for each specific case.
APA, Harvard, Vancouver, ISO, and other styles
6

Correale, Jean Claude. "Microservices from frameworks to domain specific languages." Master's thesis, Alma Mater Studiorum - Università di Bologna, 2020.

Find full text
Abstract:
This thesis explores the current state of microservice-based architectures, with particular emphasis on how microservices-based systems are structured and implemented and what are the limitations of today’s most common approaches which are essentially based on the use of Software Frameworks. Furthemore, we discuss methods to reduce the impact of such limitations and improve microservice development by means of techniques based on Domain Specific Languages and Software Factories. At the same time, an effort is made to move towards a more precise definition of what microservices are with reference to two primary aspects of any distributed system: a) the nature of the system as a whole in terms of structure, behavior and interaction between its components; b) the nature of the system’s components themselves, i.e. microservices. Microservices are therefore characterized as systems by proposing a further partitioning into smaller entities, referred to as nanoservices, that can be implemented as actors in the Actor Model sense, thus applying the microservice architectural pattern to the design and development of individual microservice. Finally, all results are aggregated into a comprehensive conceptual framework whose purpose is to provide guidelines in order deal with the problem of creating microservice-based systems.
APA, Harvard, Vancouver, ISO, and other styles
7

Shafabakhsh, Benyamin. "Research on Interprocess Communication in Microservices Architecture." Thesis, KTH, Skolan för elektroteknik och datavetenskap (EECS), 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-277940.

Full text
Abstract:
With the substantial growth of cloud computing over the past decade, microservices has gained significant popularity in the industry as a new architectural pattern. It promises a cloud-native architecture that breaks large applications into a collection of small, independent, and distributed packages. Since microservices-based applications are distributed, one of the key challenges when designing an application is the choice of mechanism by which services communicate with each other. There are several approaches for implementing Interprocess communication (IPC) in microservices, and each comes with different advantages and trade-offs. While theoretical and informal comparison exists between them, this thesis has taken an experimental approach to compare and contrast common forms of IPC communications. In this the- sis, IPC methods have been categorized into Synchronous and Asynchronous categories. The Synchronous type consists of REST API and Google gRPC, while the Asynchronous type is using a message broker known as RabbitMQ. Further, a collection of microservices for an e-commerce scenario has been designed and developed using all the three IPC methods. A load test has been executed against each model to obtain quantitative data related to Performance Efficiency, and Availability of every method. Developing the same set of functionalities using different IPC methods has offered a qualitative data related to Scalability, and Complexity of each IPC model. The evaluation of the experiment indicates that, although there is no universal IPC solution that can be applied in all cases, Asynchronous IPC patterns shall be the preferred option when designing the system. Nevertheless, the findings of this work also suggest there exist scenarios where Synchronous patterns can be more suitable.
Med den kraftiga tillväxten av molntjänster under det senaste decenniet har mikrotjänster fått en betydande popularitet i branschen som ett nytt arkitektoniskt mönster. Det erbjuder en moln-baserad arkitektur som delar stora applikationer i en samling små, oberoende och distribuerade paket. Eftersom microservicebaserade applikationer distribueras och körs på olika maskiner, är en av de viktigaste utmaningarna när man utformar en applikation valet av mekanism med vilken tjänster kommunicerar med varandra. Det finns flera metoder för att implementera Interprocess-kommunikation (IPC) i mikrotjänster och var och en har olika fördelar och nackdelar. Medan det finns teoretisk och in- formell jämförelse mellan dem, har denna avhandling tagit ett experimentellt synsätt för att jämföra och kontrastera vanliga former av IPC-kommunikation. I denna avhandling har IPC-metoder kategoriserats i synkrona och asynkrona kategorier. Den synkrona typen består av REST API och Google gRPC, medan asynkron typ använder en meddelandemäklare känd som RabbitMQ. Dessutom har en samling mikroservice för ett e-handelsscenario utformats och utvecklats med alla de tre olika IPC-metoderna. Ett lasttest har utförts mot var- je modell för att erhålla kvantitativa data relaterade till prestandaeffektivitet, och tillgänglighet för varje metod. Att utveckla samma uppsättning funktionaliteter med olika IPC-metoder har erbjudit en kvalitativ data relaterad till skalbarhet och komplexitet för varje IPC-modell. Utvärderingen av experimentet indikerar att även om det inte finns någon universell IPC-lösning som kan tillämpas i alla fall, ska asynkrona IPC-mönster vara det föredragna alternativet vid utformningen av systemet. Ändå tyder resultaten från detta arbete också på att det finns scenarier där synkrona mönster är mer lämpliga.
APA, Harvard, Vancouver, ISO, and other styles
8

De, Alwis Adambarage. "Microservice-based reengineering of enterprise systems for cloud migration." Thesis, Queensland University of Technology, 2021. https://eprints.qut.edu.au/211471/1/Adambarage_De%20Alwis_Thesis.pdf.

Full text
Abstract:
Enterprise systems, such as enterprise resource planning and customer relationship management are widely used in corporate sectors and are notoriously large and monolithic. They are challenging to decouple because they manage asynchronous, user-driven business processes and business objects (BOs) having complex structural relationships. This thesis presents the remodularization technique combined with novel microservice patterns which utilizes both semantic properties of enterprise systems, i.e., BO structure, together with syntactic features of their code, i.e., methods and interactions, for identifying suitable parts of enterprise systems which can be run as fine-grained microservices in highly scalable Cloud systems while achieving high performance characteristics.
APA, Harvard, Vancouver, ISO, and other styles
9

Sundberg, Alexander. "A study on load balancing within microservices architecture." Thesis, Högskolan i Halmstad, Akademin för informationsteknologi, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:hh:diva-38902.

Full text
Abstract:
This study addresses load balancing algorithms for networked systems with microservices architecture. In microservices applications, functionality and logic have been split into small pieces referred to as services. Such divisions allow for higher levels of scalability and distributivity than obtainable for more classical architectures where functionality and logic is packaged into large non-separable applications. As a first step, we investigate existing load balancing algorithms in the literature. A conclusion reached from this literature survey is that there is a lack of proposed load balancing algorithms for microservices, and it is not obvious how to adapt such algorithms to the architecture under consideration. In particular, many existing algorithms incorporate queues, which should be avoided for microservices, where the small services should be provided in fast manner. Hence, we provide modified and new candidates for load balancing, where one such is a probabilistic approach including a distribution that is a function of service providers' load. The algorithms are implemented in microservices simulation environment developed in Erlang by Ericsson AB. We consider a range of scenarios for evaluation, where amongst other things, we vary the number of service consumers and providers. To evaluate the load balancing algorithms, we perform statistical analysis, where first and second order moments are computed for relevant metrics under the different scenarios considered. A conclusion drawn from the results is that the algorithm referred to as "Round Robin" performed best according to the results from various simulation scenarios. This study serves as a stepping stone for further investigations. We outline several possible extensions such as more in-depth statistical analysis accounting for the time-varying aspects of the systems (currently omitted), as well other classes of algorithms.
APA, Harvard, Vancouver, ISO, and other styles
10

Camargo, André Stangarlin de. "Uma abordagem para testes de desempenho de microservices." reponame:Repositório Institucional da UFSC, 2016. https://repositorio.ufsc.br/xmlui/handle/123456789/176664.

Full text
Abstract:
Dissertação (mestrado) - Universidade Federal de Santa Catarina, Centro Tecnológico, Programa de Pós-Graduação em Ciência da Computação, Florianópolis, 2016.
Made available in DSpace on 2017-06-27T04:06:49Z (GMT). No. of bitstreams: 1 346332.pdf: 1717247 bytes, checksum: 110e4bdc3b5f8dcc17864c38b96df67b (MD5) Previous issue date: 2016
Em aplicações de grande porte é essencial reduzir o acoplamento entre módulos. Dessa forma, é possível reduzir o impacto das alterações em componentes distintos, bem como aprimorá-los de forma independente. Assim, surgiu o conceito de microservices, apresentado como uma alternativa ao modelo tradicional, conhecido como aplicações monolíticas. O modelo tradicional é criticado devido à difícil manutenção e evolução, ocasionada pelo elevado grau de acoplamento entre os componentes (FOWLER-LEWIS, 2014).A arquitetura de microservices prevê a separação de uma aplicação em um conjunto de serviços de menor complexidade, cada qual executando de forma independente e utilizando protocolos simples para comunicação, como HTTP (FOWLER-LEWIS, 2014). O modelo vem sendo amplamente utilizado, principalmente pela facilidade na manutenção e evolução das aplicações. A adoção desse modelo de arquitetura acaba por transformar uma única aplicação monolítica em um conjunto de serviços (NEWMAN, 2015), que tende a crescer com a adição de novas funcionalidades.No âmbito de microservices, existe a necessidade de prover garantias de Qualidade de Serviço (QoS), em relação a requisitos não funcionais como: disponibilidade, confiança, segurança e desempenho (MANI-NAGARAJAN, 2002). Em se tratando especificamente do campo desempenho, é necessário conhecer a capacidade e o tempo de resposta de um serviço para que se possa avaliar melhorias e correções sob a perspectiva dessas métricas.A proposta do presente trabalho é definir um modelo arquitetural que possa automatizar os testes de desempenho dos serviços em um conjunto de microservices. O problema foi endereçado à arquitetura de microservices em virtude desta representar o contexto no qual o conhecimento da capacidade dos serviços é de extrema importância, sobretudo devido à dinamicidade que os8serviços possuem, sendo que novas mudanças e funcionalidades tendem a alterar a capacidade do serviço.Com base na arquitetura proposta foi desenvolvido um framework que implementa os conceitos propostos pela arquitetura. A avaliação do framework demonstrou que o mesmo pode ser utilizado sem qualquer prejuízo ao desempenho do serviço.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Microservices"

1

Bucchiarone, Antonio, Nicola Dragoni, Schahram Dustdar, Patricia Lago, Manuel Mazzara, Victor Rivera, and Andrey Sadovykh, eds. Microservices. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-31646-4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Hunter II, Thomas. Advanced Microservices. Berkeley, CA: Apress, 2017. http://dx.doi.org/10.1007/978-1-4842-2887-6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Rajasekharaiah, Chandra. Cloud-Based Microservices. Berkeley, CA: Apress, 2021. http://dx.doi.org/10.1007/978-1-4842-6564-2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Hochrein, Akos. Designing Microservices with Django. Berkeley, CA: Apress, 2019. http://dx.doi.org/10.1007/978-1-4842-5358-8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Indrasiri, Kasun, and Prabath Siriwardena. Microservices for the Enterprise. Berkeley, CA: Apress, 2018. http://dx.doi.org/10.1007/978-1-4842-3858-5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Familiar, Bob. Microservices, IoT, and Azure. Berkeley, CA: Apress, 2015. http://dx.doi.org/10.1007/978-1-4842-1275-2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Vohra, Deepak. Kubernetes Microservices with Docker. Berkeley, CA: Apress, 2016. http://dx.doi.org/10.1007/978-1-4842-1907-2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Carneiro, Cloves, and Tim Schmelmer. Microservices From Day One. Berkeley, CA: Apress, 2016. http://dx.doi.org/10.1007/978-1-4842-1937-9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Christudas, Binildas. Practical Microservices Architectural Patterns. Berkeley, CA: Apress, 2019. http://dx.doi.org/10.1007/978-1-4842-4501-9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Oliveira Rocha, Hugo Filipe. Practical Event-Driven Microservices Architecture. Berkeley, CA: Apress, 2022. http://dx.doi.org/10.1007/978-1-4842-7468-2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "Microservices"

1

de Toledo, Saulo S., Antonio Martini, and Dag I. K. Sjøberg. "Improving Agility by Managing Shared Libraries in Microservices." In Agile Processes in Software Engineering and Extreme Programming – Workshops, 195–202. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-58858-8_20.

Full text
Abstract:
Abstract Using microservices is a way of supporting an agile architecture. However, if the microservices development is not properly managed, the teams’ development velocity may be affected, reducing agility and increasing architectural technical debt. This paper investigates how to manage the use of shared libraries in microservices to improve agility during development. We interviewed practitioners from four large international companies involved in microservices projects to identify problems when using shared libraries. Our results show that the participating companies had issues with shared libraries as follows: coupling among teams, delays on fixes due to overhead on libraries development teams, and need to maintain many versions of the libraries. Our results highlight that the use of shared libraries may hinder agility on microservices. Thus, their use should be restricted to situations where shared libraries cannot be replaced by a microservice and the costs of replicating the code on each service is very high.
APA, Harvard, Vancouver, ISO, and other styles
2

Gutierrez, Felipe. "Microservices." In Spring Boot Messaging, 179–92. Berkeley, CA: Apress, 2017. http://dx.doi.org/10.1007/978-1-4842-1224-0_11.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Merelo, J. J. "Microservices." In Raku Recipes, 197–234. Berkeley, CA: Apress, 2020. http://dx.doi.org/10.1007/978-1-4842-6258-0_11.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Starke, Gernot. "Microservices." In Effektive Softwarearchitekturen, 339–50. München: Carl Hanser Verlag GmbH & Co. KG, 2020. http://dx.doi.org/10.3139/9783446465893.010.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Comer, Douglas E. "Microservices." In The Cloud Computing Book, 163–78. Boca Raton: Chapman and Hall/CRC, 2021. http://dx.doi.org/10.1201/9781003147503-16.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Heusingfeld, Alex. "Microservices." In Effektive Softwarearchitekturen, 337–48. München: Carl Hanser Verlag GmbH & Co. KG, 2017. http://dx.doi.org/10.3139/9783446454200.010.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Fouda, Engy. "Microservices." In A Complete Guide to Docker for Operations and Development, 105–19. Berkeley, CA: Apress, 2022. http://dx.doi.org/10.1007/978-1-4842-8117-8_9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Baresi, Luciano, and Martin Garriga. "Microservices: The Evolution and Extinction of Web Services?" In Microservices, 3–28. Cham: Springer International Publishing, 2019. http://dx.doi.org/10.1007/978-3-030-31646-4_1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Autili, Marco, Alexander Perucci, and Lorenzo De Lauretis. "A Hybrid Approach to Microservices Load Balancing." In Microservices, 249–69. Cham: Springer International Publishing, 2019. http://dx.doi.org/10.1007/978-3-030-31646-4_10.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Ciavotta, Michele, Giovanni Dal Maso, Diego Rovere, Radostin Tsvetanov, and Silvia Menato. "Towards the Digital Factory: A Microservices-Based Middleware for Real-to-Digital Synchronization." In Microservices, 273–97. Cham: Springer International Publishing, 2019. http://dx.doi.org/10.1007/978-3-030-31646-4_11.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Microservices"

1

Bychkov, I. V., G. A. Oparin, V. G. Bogdanova, and A. A. Pashinin. "Intellectual technology for computation control in the package of applied microservices." In The International Workshop on Information, Computation, and Control Systems for Distributed Environments 2019. Crossref, 2019. http://dx.doi.org/10.47350/iccs-de.2019.02.

Full text
Abstract:
The complexity of exhaustive problems with the properties of large-scale, openness, unpredictable dynamics, and component mobility determines the relevance of developing microservice-oriented software for their solving in a hybrid computational environment. We propose an approach for adapting to this environment both the existing software and new ones developed using new automated technology for creating an applied microservice package and organizing control of computations in it. The distributed computational model is represented by a set of small, loosely coupled, replaceable, interacting with the use of lightweight communication mechanisms autonomous microservices that implement the functions of the program package modules. The decentralized management of the microservices interaction is carried out by a self-organizing multi-agent system, agents of which are delegated the rights to launch microservices. The paper discusses the models, methods, and software platform that form the basis of the proposed technology. We demonstrate the application of the applied microservice package, based on this technology, for solving the problems of qualitative analysis of binary dynamic system using the author's Boolean constraints method.
APA, Harvard, Vancouver, ISO, and other styles
2

Rocha, Fabio Gomes, Michel S. Soares, and Guillermo Rodriguez. "Patterns in Microservices-based Development: A Grey Literature Review." In Congresso Ibero-Americano em Engenharia de Software. Sociedade Brasileira de Computação, 2023. http://dx.doi.org/10.5753/cibse.2023.24693.

Full text
Abstract:
Microservices emerged due to the massive adoption of cloud computing and the need to integrate legacy systems. However, there still needs to be a greater understanding of adopting a microservice-based architectural style. Besides, there is a need for guidelines to operationalize those microservices. We conducted a grey literature review to identify commonly used architectural patterns and how they are implemented following design patterns. We present two key contributions. Firstly, we identified four architectural patterns and 23 design patterns. Secondly, we identified a catalog of tools for implementing the main patterns adopted when using the microservices style. The Proxy and the SAGA patterns are the most used in communicating and linking data for services. Additionally, tools such as Kubernetes, Docker, and Amazon WS are the most used for implementing microservices and deploying them into containers.
APA, Harvard, Vancouver, ISO, and other styles
3

Barretto, Wagner Rezende Muniz, Ana Cristina B. Kochem Vendramin, and Mauro Fonseca. "RW-Through: A Data Replication Protocol Suitable for GeoDistributed and Read-Intensive Workloads." In XVII Workshop em Clouds e Aplicações. Sociedade Brasileira de Computação - SBC, 2019. http://dx.doi.org/10.5753/wcga.2019.7592.

Full text
Abstract:
The microservice architecture encourages the composition of services through choreography. Choreography favors loose coupling and decentralization. The challenge then arises of finding suitable approaches for carrying it out according to the architectural style proposed by the microservices. This paper describes and compares two strategies for choreographing microservices. The first strategy is event based and makes use of a mediator to convey the messages. The second is called choreographic programming and its great advantage is to provide an overview of choreography. A case study with four microservices was implemented in each strategy. Results include a comparative table and the number of messages per minute supported by implementations.
APA, Harvard, Vancouver, ISO, and other styles
4

Oparin, G. A., V. G. Bogdanova, and A. A. Pashinin. "Automation of distributed data management in applied microservices package for scientific computations." In The International Workshop on Information, Computation, and Control Systems for Distributed Environments. Crossref, 2020. http://dx.doi.org/10.47350/iccs-de.2020.20.

Full text
Abstract:
We offer a specialized toolkit for automating both knowledge management when creating an applied microservices package and data accumulating during its application for scientific computations in a hybrid computing environment. The decentralized solving of the declaratively formulated problem is carried out by an active agent group. This group is self-organized by logical inference on the distributed knowledge base of a subject domain. The developed toolkit automates the creating and updating of the local knowledge base of the manager-agent of applied microservices package, as well as the local knowledge bases of distributed computational agents. Local knowledge bases are formed using a description of the interface of computational microservices managed by these agents. Microservice ensembles, corresponding to the active group, are stored in the knowledge base of the manager-agent. The developed toolkit uses this information for testing microservice in the case of its update. In hybrid computing, this toolkit provides synchronizing, archiving, and saving of calculated data. Hybrid infrastructure combines the reliability and availability of using on-premises computers with scaling to the cloud when peak loads occur. The conducted experiments confirmed the effectiveness of the presented approach for solving practically significant scientific problems.
APA, Harvard, Vancouver, ISO, and other styles
5

Nunes, João Paulo K. S., Thiago Bianchi, Anderson Y. Iwasaki, and Elisa Yumi Nakagawa. "State of the Art on Microservices Autoscaling: An Overview." In Seminário Integrado de Software e Hardware. Sociedade Brasileira de Computação - SBC, 2021. http://dx.doi.org/10.5753/semish.2021.15804.

Full text
Abstract:
The adoption of microservices architecture has taken on great pro-portions due to its benefits and popularization of containers driven tools, such as Kubernetes and Docker. Besides, the development of microservice-based applications is a complex task, specially because they can be composed of multiple heterogeneous parts. In particular, one of the main challenges is how to conduct the microservices autoscaling (i.e., adding or removing resources on demand), while still avoiding resource waste, such as CPU and memory. This paper presents the state of the art of approaches to solve the problem of micro services autoscaling, the main characteristics to be considered as well as the important future directions that need to be still investigated.
APA, Harvard, Vancouver, ISO, and other styles
6

Alencar, Derian, Helder Oliveira, and Denis Rosário. "Dynamic allocation of microservices for virtual reality content delivery to provide quality of experience support in a fog computing architecture." In Concurso de Teses e Dissertações. Sociedade Brasileira de Computação - SBC, 2023. http://dx.doi.org/10.5753/ctd.2023.230102.

Full text
Abstract:
Virtual Reality (VR) content is gaining popularity and allowing users to immerse themselves in a new world over the Internet. However, the high-demand for resources and the low latency requirements of VR services require changes in the current 5G networks to deliver VR with quality assurance. Microservices present a suitable model for deploying services at different levels of a 5G fog computing architecture for managing traffic and providing Quality of Experience (QoE) guarantees to VR clients. However, finding the most suitable fog node to allocate microservices for VR clients in QoE-aware 5G scenarios is a difficult task. This article proposes a QoE VR-based mechanism for allocating microservice dynamically in 5G architectures, called Fog4VR. Fog4VR determines the optimal fog node to allocate the VR microservice based on delay, migration time, and resource utilization rate. This article also presents the INFORMER, an integer linear programming model aiming to find the optimal global solution for microservice allocation. Results obtained with INFORMER serve as a baseline to evaluate Fog4VR in different scenarios using a simulation environment. Results demonstrate the capabilities of Fog4VR compared to existing mechanisms in QoE, migration time, fairness index, and terms of cost.
APA, Harvard, Vancouver, ISO, and other styles
7

Stefan, Livia. "BLOCKCHAIN TECHNOLOGIES AND MICROSERVICES FOR OPEN LEARNING COMMUNITIES. A SOFTWARE ARCHITECTURE PERSPECTIVE." In eLSE 2020. University Publishing House, 2020. http://dx.doi.org/10.12753/2066-026x-20-186.

Full text
Abstract:
It is a well-known fact that innovative e-learning concepts have pushed IT technologies to new levels of development or, reciprocally, innovative or even disrupting technologies have opened new possibilities for elearning. There are many examples of IT technologies that contributed to new or improved learning paradigms and styles, such as social networks, mobile devices, augmented and virtual reality, MOOCs and distributed computing. Recently, several research works discuss how the blockchain concepts and technologies can be applied not only in cryptocurrency, but also on elearning and educational processes with an essential impact, e.g. de-centralization of resources, open learning, tokenization of elearning, authenticity and security of information and resources. The current research paper will address how blockchain can be utilized with microservice based architectures, based on similarities, to support the most modern trends in education, such as open learning communities. In the first part of the paper, the main concepts and mechanisms behind the blockchain technologies are reviewed and explained in comparison with concepts and characteristics of microservices, considered a similar architectural pattern. Blockchain relies on the existing algorithms (such as cryptography) and distributed computing to bring new concepts such as ledgers and smart contracts. Likewise, microservices have roots on Service-Oriented Architecture (SOA) and Application Programming Interfaces (API). Microservices represent a new arhitectural pattern, to change the traditional way of software development resulting in "application monoliths" to a true modularization by means of composition of standalone software components (microservices), having well-defined functionality, securely exposed to other microservices or applications. In the second part, a software architecture leveraging blockchain smart contract and microservices to support open learning communities, unique identity, secure storage and retrieval of resources will be proposed and described.
APA, Harvard, Vancouver, ISO, and other styles
8

Matlekovic, Lea, and Peter Schneider-Kamp. "From Monolith to Microservices: Software Architecture for Autonomous UAV Infrastructure Inspection." In 11th International Conference on Embedded Systems and Applications (EMSA 2022). Academy and Industry Research Collaboration Center (AIRCC), 2022. http://dx.doi.org/10.5121/csit.2022.120622.

Full text
Abstract:
Linear-infrastructure Mission Control (LiMiC) is an application for autonomous Unmanned Aerial Vehicle (UAV) infrastructure inspection mission planning developed in monolithic software architecture. The application calculates routes along the infrastructure based on the users’ inputs, the number of UAVs participating in the mission, and UAVs’ locations. LiMiC1.0 is the latest application version migrated from monolith to microservices, continuously integrated, and deployed using DevOps tools to facilitate future features development, enable better traffic management, and improve the route calculation processing time. Processing time was improved by refactoring the route calculation algorithm into services, scaling them in the Kubernetes cluster, and enabling asynchronous communication in between. In this paper, we discuss the differences between the monolith and microservice architecture to justify our decision for migration. We describe the methodology for the application’s migration and implementation processes, technologies we use for continuous integration and deployment, and we present microservices improved performance results compared with the monolithic application.
APA, Harvard, Vancouver, ISO, and other styles
9

Krause, Lucas. "Microservices." In Applicative 2016. New York, New York, USA: ACM Press, 2016. http://dx.doi.org/10.1145/2959689.2960082.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Shadija, Dharmendra, Mo Rezai, and Richard Hill. "Microservices." In UCC '17: 10th International Conference on Utility and Cloud Computing. New York, NY, USA: ACM, 2017. http://dx.doi.org/10.1145/3147234.3148093.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Microservices"

1

Klein, Brandon Thorin, Gerald Giese, Jayson Lane, John Gifford Miner, John J. Jones, and Otoniel Venezuela. An Approach to DevOps and Microservices. Office of Scientific and Technical Information (OSTI), March 2020. http://dx.doi.org/10.2172/1635752.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Chandramouli, Ramaswamy. Security strategies for microservices-based application systems. Gaithersburg, MD: National Institute of Standards and Technology, August 2019. http://dx.doi.org/10.6028/nist.sp.800-204.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Chandramouli, Ramaswamy, and Zack Butcher. Building secure microservices-based applications using service-mesh architecture. Gaithersburg, MD: National Institute of Standards and Technology, May 2020. http://dx.doi.org/10.6028/nist.sp.800-204a.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Chandramouli, Ramaswamy. Implementation of DevSecOps for a Microservices-based Application with Service Mesh. National Institute of Standards and Technology, September 2021. http://dx.doi.org/10.6028/nist.sp.800-204c-draft.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Chandramouli, Ramaswamy. Implementation of DevSecOps for a Microservices-based Application with Service Mesh. National Institute of Standards and Technology, March 2022. http://dx.doi.org/10.6028/nist.sp.800-204c.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Chandramouli, Ramaswamy, Zack Butcher, and Aradhna Chetal. Attribute-based Access Control for Microservices-based Applications Using a Service Mesh. National Institute of Standards and Technology, August 2021. http://dx.doi.org/10.6028/nist.sp.800-204b.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Chandramouli, Ramaswamy. Securing the Artifacts in Software Supply Chain for Building Cloud-Native Microservices Applications. Gaithersburg, MD: National Institute of Standards and Technology, 2023. http://dx.doi.org/10.6028/nist.sp.800-204d.ipd.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Brim, Michael, and Christian Engelmann. INTERSECT Architecture Specification: Microservice Architecture (Version 0.9). Office of Scientific and Technical Information (OSTI), September 2023. http://dx.doi.org/10.2172/2333815.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Brim, Michael, and Christian Engelmann. INTERSECT Architecture Specification: Microservice Architecture (Version 0.5). Office of Scientific and Technical Information (OSTI), September 2022. http://dx.doi.org/10.2172/1902805.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Microservices' for particular source types:
Journal articles Dissertations / Theses Books
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography