Добірка наукової літератури з теми "Architecture à base de microservices"
Оформте джерело за APA, MLA, Chicago, Harvard та іншими стилями
Ознайомтеся зі списками актуальних статей, книг, дисертацій, тез та інших наукових джерел на тему "Architecture à base de microservices".
Біля кожної праці в переліку літератури доступна кнопка «Додати до бібліографії». Скористайтеся нею – і ми автоматично оформимо бібліографічне посилання на обрану працю в потрібному вам стилі цитування: APA, MLA, «Гарвард», «Чикаго», «Ванкувер» тощо.
Також ви можете завантажити повний текст наукової публікації у форматі «.pdf» та прочитати онлайн анотацію до роботи, якщо відповідні параметри наявні в метаданих.
Статті в журналах з теми "Architecture à base de microservices"
1
Jaskot, Kamil, and Sławomir Przyłucki. "Analysis of selected features of application based on monolithic and microservice architecture." Journal of Computer Sciences Institute 25 (December 30, 2022): 393–400. http://dx.doi.org/10.35784/jcsi.3061.
Повний текст джерелаАнотація:
The article describes the performance of applications built in monolithic and microservice architectures. The base of research includes application supporting prescription management developed with the use of Spring Framework technology and implemented in the Docker Swarm test environment. The tested applications were subjected to various loads in the form of sending HTTP requests that simulated user behaviour. The research has proven that an application created based on microservices architecture offers better traffic handling in case of high load. Scaling a microservice application allows for greater gains in performance measured as quantity served client requests per unit of time than scaling a monolithic application under the same conditions scaling.
2
Doljenko, Alexey, Irina Shpolianskaya, and Sergey Glushenko. "Fuzzy production network model for quality assessment of an information system based on microservices." Business Informatics 14, no. 4 (December 31, 2020): 36–46. http://dx.doi.org/10.17323/2587-814x.2020.4.36.46.
Повний текст джерелаАнотація:
This article describes the analysis of the quality of microservice architectures, which are one of the main approaches to the creation and maintenance of modern information systems capable of quickly respond to changes in business demands. The implementation of continuous delivery of software components for dynamic business processes of information systems can be carried out by various sets of microservices, the optimal choice of which is a complex multi-alternative task. The paper presents a review of existing approaches to solving the problem, which showed that the development of models for assessing the quality of microservices of information systems requires further elaboration in terms of accounting for uncertainty in the initial data and modes of operation. The authors have proposed an approach to solving the problem of analyzing the quality of a microservice architecture which is implemented on the basis of a fuzzy production network model. The model allows for comprehensive accounting of various parameters (qualitative and quantitative). The article shows the implementation process of the fuzzy production network that was developed to analyze the functional quality of the microservice architecture for processing customer orders using fuzzy modeling software. The results of the analysis will allow managers and system architects to make an informed choice of the microservice architecture of the information system, as well as use it in their reports when arguing the need for scaling the system and increasing the availability of microservices.
3
Havano, Bohdan, and Mykola Morozov. "Assessing the Human Condition in Medical Cyber-Physical System Based on Microservices Architecture." Advances in Cyber-Physical Systems 6, no. 2 (December 17, 2021): 112–20. http://dx.doi.org/10.23939/acps2021.02.112.
Повний текст джерелаАнотація:
The goal of the work is to propose architectural and information model for assessing the human condition on the basis of microservice architecture in medical cyber-physical system, which, in contrast to the known models for assessing the human condition, can simultaneously provide scaling, fault tolerance and increase the speed of human condition assessment. The theoretical substantiation and the new decision of an actual scientific problem of development and research means of an estimation of a human condition in medical cyber-physical system have been considered. These means involve the parallel processing of data on vital signs of the human condition, organizing the means of information processing into separate independent logical elements — microservices, in comparison with other existing medical cyber-physical systems. An architectural model based on microservice architecture has been proposed.
4
Barabanov, Alexander, and Denis Makrushin. "Authentication and Authorization in Microservice-Based Systems: Survey of Architecture Patterns." Voprosy kiberbezopasnosti, no. 4(38) (2020): 32–43. http://dx.doi.org/10.21681/2311-3456-2020-04-32-43.
Повний текст джерелаАнотація:
Abstract Objective. Service-oriented architecture and its microservice-based approach increase an attack surface of applications. Exposed microservices become a pivot point for advanced persistent threats and completely change the threat landscape. Correctly implemented authentication and authorization architecture patterns are basis of any software maturity program. The aim of this study is to provide a helpful resource to application security architect and developers on existing architecture patterns to implement authentication and authorization in microservices-based systems. Method. In this paper, we conduct a systematic review of major electronic databases and libraries as well as security standards and presentations at the major security conferences. Results and practical relevance. In this work based on research papers and major security conferences presentations analysis, we identified industry best practices in authentication and authorization patterns and its applicability depending on environment characteristic. For each described patterns we reviewed its advantages and disadvantages that could be used as decision-making criteria for application security architects during architecture design phase.
5
Chimakurthi, Venkata Naga Satya Surendra. "Risks of Multi-Cloud Environment: Micro Services Based Architecture and Potential Challenges." ABC Research Alert 5, no. 3 (December 31, 2017): 33—xx. http://dx.doi.org/10.18034/abcra.v5i3.590.
Повний текст джерелаАнотація:
Over the most recent couple of years, a modified programming engineering style has been created to plan new programming applications. This engineering style is especially appropriate for use cases in the avionic business, from an autonomously deployable programming administration. These administrations are worked around business and mission capacities and are freely deployable by completely computerized apparatus. With microservices, a few sorts of uses become simpler to construct and keep up with when they are separated into more modest, composable pieces that cooperate. This is rather than a conventional, "solid" application that is completely evolved in one piece. This paper will talk about, a few parts of microservices-based engineering, including a few potential use cases for the aeronautic trade. The qualities of microservice-based engineering like componentization, association, endpoints, and informing systems. The specialized execution of microservices by auditing containerization, administrations correspondence, and related design parts. Explicit open-source tasks and parts that can be used to fabricate the microservices-based design. An example set of utilization cases.
6
Kazanavičius, Justas, Dalius Mažeika, and Diana Kalibatienė. "An Approach to Migrate a Monolith Database into Multi-Model Polyglot Persistence Based on Microservice Architecture: A Case Study for Mainframe Database." Applied Sciences 12, no. 12 (June 17, 2022): 6189. http://dx.doi.org/10.3390/app12126189.
Повний текст джерелаАнотація:
Migration from a monolithic architecture to a microservice architecture is a complex challenge, which consists of issues such as microservices identification, code decomposition, commination between microservices, independent deployment, etc. One of the key issues is data storage adaptation to a microservice architecture. A monolithic architecture interacts with a single database, while in microservice architecture, data storage is decentralized, each microservice works independently and has its own private data storage. A viable option to fulfil different microservice persistence requirements is polyglot persistence, which is data storage technology selected according to the characteristics of each microservice need. This research aims to propose and evaluate the approach of monolith database migration into multi-model polyglot persistence based on microservice architecture. The novelty and relevance of the proposed approach are double, that is, it provides a general approach of how to conduct database migration from monolith architecture into a microservice architecture and allows the data model to be transformed into multi-model polyglot persistence. Migration from a mainframe monolith database to a multi-model polyglot persistence was performed as a proof-of-concept for the proposed migration approach. Quality attributes defined in the ISO/IEC 25012:2008 standard were used to evaluate and compare the data quality of the microservice with the multi-model polyglot persistence and the existing monolith mainframe database. Results of the research showed that the proposed approach can be used to conduct data storage migration from a monolith to microservice architecture and improve the quality of the consistency, understandability, availability, and portability attributes. Moreover, we expect that our results could inspire researchers and practitioners toward further work aimed to improve and automate the proposed approach.
7
Suljkanović, Alen, Branko Milosavljević, Vladimir Inđić, and Igor Dejanović. "Developing Microservice-Based Applications Using the Silvera Domain-Specific Language." Applied Sciences 12, no. 13 (July 1, 2022): 6679. http://dx.doi.org/10.3390/app12136679.
Повний текст джерелаАнотація:
Microservice Architecture (MSA) is a rising trend in software architecture design. Applications based on MSA are distributed applications whose components are microservices. MSA has already been adopted with great success by numerous companies, and a significant number of published papers discuss its advantages. However, the results of recent studies show that there are several important challenges in the adoption of microservices such as finding the right decomposition approach, heterogeneous technology stacks, lack of relevant skills, out-of-date documentation, etc. In this paper, we present Silvera, a Domain-Specific Language (DSL), and a compiler for accelerating the development of microservices. Silvera is a declarative language that allows users to model the architecture of microservice-based systems. It is designed so that it can be used both by inexperienced and experienced developers. The following characteristics distinguish Silvera from similar tools: (i) lightweight and editor-agnostic language, (ii) built with heterogeneity in mind, (iii) uses microservice-tailored metrics to evaluate the architecture of the designed system, and (iv) automatically generates the documentation. Silvera’s retargetable compiler transforms models into runnable code and produces the documentation for each microservice in the model. The compiler can produce code for any programming language or framework since code generators are registered as plugins. We present a case study that illustrates the use of Silvera and also discuss some current limitations and development directions. To evaluate Silvera, we conducted a survey based on A Framework for Qualitative Assessment of DSLs (FQAD), where we focused on the following DSL characteristics: functional suitability, usability, reliability, productivity, extendability, and expressiveness. Overall, the survey results show that Silvera satisfies these characteristics.
8
Yu, Hang, Xiulei Wang, Changyou Xing, and Bo Xu. "A Microservice Resilience Deployment Mechanism Based on Diversity." Security and Communication Networks 2022 (June 1, 2022): 1–13. http://dx.doi.org/10.1155/2022/7146716.
Повний текст джерелаАнотація:
The microservice architecture has many advantages, such as technology heterogeneity, isolation, scalability, simple deployment, and convenient optimization. These advantages are important as we can use diversity and redundancy to improve the resilience of software system. It is necessary to study the method of improving the resilience of software system by diversity implementation and redundant deployment of software core components based on microservice framework. How to optimize the diversity deployment of microservices is a key problem to maximize system resilience and make full use of resources. To solve this problem, an efficient microservice diversity deployment mechanism is proposed in this paper. Firstly, we creatively defined a load balancing indicator and a diversity indicator. Based on this, a diversified microservices deployment model is established to maximize the resilience and the resource utilization of the system. Secondly, combined with load balancing, a microservice deployment algorithm based on load balance and diversity is proposed, which reduces the service’s dependence on the underlying mirror by enriching diversity and avoids the overreliance of microservices on a single node through decentralized deployment, while taking into account load balancing. Finally, we conduct experiments to evaluate the performance of the proposed algorithm. The results demonstrate that the proposed algorithm outperforms other algorithms.
9
Dontsov, Alexander A., and Igor A. Sutorikhin. "DEVELOPMENT OF A GEOGRAPHIC INFORMATION SYSTEM BASED ON MICROSERVICE ARCHITECTURE." Interexpo GEO-Siberia 4, no. 1 (May 21, 2021): 41–44. http://dx.doi.org/10.33764/2618-981x-2021-4-1-41-44.
Повний текст джерелаАнотація:
The paper discusses the use of microservice architecture in the development of distributed geographic information systems (GIS) for collecting, processing and analyzing data. Microservice architecture is used to build applications in information systems related to solving business problems, and is not widespread in the development of geographic information systems in the scientific field. However, its application is now becoming increasingly important. Decomposition of the software implementation and GIS infrastructure associated with computations and data processing into components in the form of microservices has a number of advantages, such as: increased fault tolerance, increased flexibility, reduced maintenance effort, simplified scaling, and others. The first results of the application of the microservice approach in the development of a geoinformation system for the collection and processing of hydrological and hydrobiological data on the state of water bodies are shown. The architecture, main components, and features of building infrastructure are shown.
10
Kuruoglu Dolu, Betul, Anil Cetinkaya, M. Cagri Kaya, Selma Nazlioglu, and Ali H. Dogru. "MSDeveloper: A Variability-Guided Methodology for Microservice-Based Development." Applied Sciences 12, no. 22 (November 11, 2022): 11439. http://dx.doi.org/10.3390/app122211439.
Повний текст джерелаАнотація:
This article presents a microservice-based development approach, MSDeveloper (Microservices Developer), employing variability management for product configuration through a low-code development environment. The purpose of this approach is to offer a general-purpose environment for the easier development of families of products for different domains: a domain-oriented development environment is suggested, where domain developers and product developers can utilize the environment as a software ecosystem. Thus, genericity is offered through supporting different domains. A domain is populated with feature and process models and microservices in a layered architecture. Feature models drive the product configuration, which affects the process model and the microservice layer. An experimental study was conducted to validate the applicability of the approach and the usability of the development environment. Students from different courses were assigned system modeling projects where they utilized helper tools supporting the provided methodology. Furthermore, professional software developers were consulted about this recommended domain-oriented development environment. Feedback from student projects and professionals’ remarks are analyzed and discussed.
Дисертації з теми "Architecture à base de microservices"
1
Wang, Yuwei. "Evolution of microservice-based applications : Modelling and safe dynamic updating." Electronic Thesis or Diss., Institut polytechnique de Paris, 2022. http://www.theses.fr/2022IPPAS009.
Повний текст джерелаАнотація:
Les architectures à base de microservices permettent de construire des systèmes répartis complexes composés de microservices indépendants. Le découplage et la modularité des microservices facilitent leur remplacement et leur mise à jour de manière indépendante. Depuis l'émergence du développement agile et de l'intégration continue (DevOps et CI/CD), la tendance est aux changements de version plus fréquents et en cours d'exécution des applications. La réalisation des changements de version est effectuée par un processus d'évolution consistant à passer de la version actuelle de l'application à une nouvelle version. Cependant, les coûts de maintenance et d'évolution de ces systèmes répartis augmentent rapidement avec le nombre de microservices.L'objectif de cette thèse est de répondre aux questions suivantes~:Comment aider les ingénieurs à mettre en place une gestion de version unifiée et efficace pour les microservices et comment tracer les changements de version dans les applications à base de microservices ?Quand les applications à base de microservices, en particulier celles dont les activités sont longues, peuvent-elles être mises à jour dynamiquement sans arrêter l'exécution de l'ensemble du système ? Comment la mise à jour doit-elle être effectuée pour assurer la continuité du service et maintenir la cohérence du système ?En réponse à ces questions, cette thèse propose deux contributions principales. La première contribution est constituée de modèles architecturaux et d'un graphe d'évolution pour modéliser et tracer la gestion des versions des microservices. Ces modèles sont construits lors de la conception et utilisés durant l'exécution. Cette contribution aide les ingénieurs à abstraire l'évolution architecturale afin de gérer les déploiements lors d'une reconfiguration, et fournit la base de connaissances nécessaire à un intergiciel de gestion autonomique des activités d'évolution. La deuxième contribution est une approche basée sur les instantanés pour la mise à jour dynamique (DSU) des applications à base de microservices. Les instantanés répartis cohérents de l'application en cours d'exécution sont construits pour être utilisés dans la spécification de la continuité du service, l'évaluation des conditions de mise à jour sûre et dans la mise en œuvre des stratégies de mise à jour. La complexité en nombre de messages de l'algorithme DSU n'est alors pas égale à la complexité de l'application répartie, mais correspond à la complexité de l'algorithme de construction d'un instantané réparti cohérentMicroservice architectures contribute to building complex distributed systems as sets of independent microservices. The decoupling and modularity of distributed microservices facilitates their independent replacement and upgradeability. Since the emergence of agile DevOps and CI/CD, there is a trend towards more frequent and rapid evolutionary changes of the running microservice-based applications in response to various evolution requirements. Applying changes to microservice architectures is performed by an evolution process of moving from the current application version to a new version. The maintenance and evolution costs of these distributed systems increase rapidly with the number of microservices.The objective of this thesis is to address the following issues: How to help engineers to build a unified and efficient version management for microservices and how to trace changes in microservice-based applications? When can microservice-based applications, especially those with long-running activities, be dynamically updated without stopping the execution of the whole system? How should the safe updating be performed to ensure service continuity and maintain system consistency?In response to these questions, this thesis proposes two main contributions. The first contribution is runtime models and an evolution graph for modelling and tracing version management of microservices. These models are built at design time and used at runtime. It helps engineers abstract architectural evolution in order to manage reconfiguration deployments, and it provides the knowledge base to be manipulated by an autonomic manager middleware in various evolution activities. The second contribution is a snapshot-based approach for dynamic software updating (DSU) of microservices. The consistent distributed snapshots of microservice-based applications are constructed to be used for specifying continuity of service, evaluating the safe update conditions and realising the update strategies. The message complexity of the DSU algorithm is not the message complexity of the distributed application, but the complexity of the consistent distributed snapshot algorithm
2
Johansson, Gustav. "Investigating differences in response time and error rate between a monolithic and a microservice based architecture." Thesis, KTH, Skolan för elektroteknik och datavetenskap (EECS), 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-264840.
Повний текст джерелаАнотація:
With great advancements in cloud computing, the microservice architecture has become a promising architectural style for enterprise software. It has been proposed to cope with problems of the traditional monolithic architecture which includes slow release cycles, limited scalability and low developer productivity. Therefore, this thesis aims to investigate the affordances and challenges of adopting microservices as well as the difference in performance compared to the monolithic approach at one of Sweden’s largest banks, SEB - the Scandinavian Individual Bank. The investigation consisted of a literature study of research papers and official documentation of microservices. Moreover, two applications were developed and deployed using two different system architectures - a monolithic architecture and a microservice architecture. Performance tests were executed on both systems to gather quantitative data for analysis. The two metrics investigated in this study were response time and error rate. The results indicate the microservice architecture has a significantly higher error rate but a slower response time than the monolithic approach, further strengthening the results of Ueda et. al. [47] and Villamizar et. al. [48]. The findings have then been discussed with regards to the challenges and complexity involved in implementing distributed systems. From this study, it becomes clear the complexity shifts from inside the application out towards infrastructure with a microservice architecture. Therefore, microservices should not be seen as a silver bullet. Rather, the type of architecture is highly dependent on the scope of the project and the size of the organization.Med stora framstegen inom molntjänster har microservice arkitekturen kommit att bli en lämplig kandidat för utveckling av företagsprogramvara. Denna typ av systemarkitektur har föreslagits att lösa de problem som den traditionella monolitiska arkitekturen medför; långsamma lanseringar, begränsad skalbarhet och låg produktivitet. Således fokuserar denna avhandling på att utforska de möjligheter samt utmaningar som följer vid adoptering av microservices samt skillnaden i prestanda jämfört med den monolitiska arkitekturen. Detta undersöktes på en av Sveriges största banker, SEB, den Skandinaviska Enskilda Banken. Utredningen bestod av en litteraturstudie av vetenskapliga artiklar samt officiell dokumentation för microservices. Dessutom utvecklades och lanserades två applikationer byggt med två olika typer av systemarkitektur - en som monolitisk arkitektur och den andra som en microservice arkitektur. Prestandatest utfördes sedan på båda systemen för att samla kvantitativ data för analys. De två nyckelvardena som undersöktes i denna studie var responstid och felfrekvens. Resultaten indikerar att microservice arkitekturen har en signifikant högre felfrekvens men en långsammare responstid än den monolitiska arkitekturen, vilket stärker resultaten av Ueda et. al. [47] och Villamizar et. al. [48]. Forskningsresultaten har diskuterats med hänsyn till den komplexitet och de utmaningar som följer vid implementering av distribuerade system. Från denna studie blir det tydligt att komplexiteten i en microservice arkitektur skiftar från inuti applikationen ut till infrastrukturen. Således borde microservices inte ses som en silverkula. Istället är valet av systemarkitektur strikt beroende på omfattningen av projektet samt storleken på organisationen i fråga.
3
Black, Alofi S. "eHealth-as-a-Service: A service based design approach for large scale eHealth architecture." Thesis, Queensland University of Technology, 2018. https://eprints.qut.edu.au/119154/1/Alofi_Black_Thesis.pdf.
Повний текст джерелаАнотація:
This thesis is an in-depth exploration of a multi-methodological design science approach to develop a purposeful eHealth-as-a-Service (eHaaS) design artifact, with potential to improve information quality in primary care settings. This was achieved by first, deriving abstract meta-requirements from an ethnographic examination of care pathways to establish the technical goals of the solution. Then, defining the functions, organization, and structure of an eHaaS conceptual model as an example of how service-based architectures might deliver high quality information services. Finally, establishing the validity of the conceptual model with the development of a novel evaluation strategy to explain the predicted change produced by eHaaS architecture. Given that, eHaas provides the foundation for developing a link between the patient and their information that is available to multiple healthcare professionals when needed.
4
Islam, J. (Johirul). "Container-based microservice architecture for local IoT services." Master's thesis, University of Oulu, 2019. http://jultika.oulu.fi/Record/nbnfioulu-201906072492.
Повний текст джерелаАнотація:
Abstract. Edge services are needed to save networking and computational resources on higher tiers, enable operation during network problems, and to help limiting private data propagation to higher tiers if the function needing it can be handled locally. MEC at access network level provides most of these features but cannot help when access network is down. Local services, in addition, help alleviating the MEC load and limit the data propagation even more, on local level. This thesis focuses on the local IoT service provisioning. Local service provisioning is subject to several requirements, related to resource/energy-efficiency, performance and reliability.
This thesis introduces a novel way to design and implement a Docker container-based micro-service system for gadget-free future IoT (Internet of Things) network. It introduces a use case scenario and proposes few possible required micro-services as of solution to the scenario. Some of these services deployed on different virtual platforms along with software components that can process sensor data providing storage capacity to make decisions based on their algorithm and business logic while few other services deployed with gateway components to connect rest of the devices to the system of solution. It also includes a state-of-the-art study for design, implementation, and evaluation as a Proof-of-Concept (PoC) based on container-based microservices with Docker. The used IoT devices are Raspberry Pi embedded computers along with an Ubuntu machine with a rich set of features and interfaces, capable of running virtualized services.
This thesis evaluates the solution based on practical implementation. In addition, the thesis also discusses the benefits and drawbacks of the system with respect to the empirical solution. The output of the thesis shows that the virtualized microservices could be efficiently utilized at the local and resource constrained IoT using Dockers. This validates that the approach taken in this thesis is feasible for providing such services and functionalities to the micro
5
Selmadji, Anfel. "From monolithic architectural style to microservice one : structure-based and task-based approaches." Thesis, Montpellier, 2019. http://www.theses.fr/2019MONTS026/document.
Повний текст джерелаАнотація:
Les technologies logicielles ne cessent d'évoluer pour faciliter le développement, le déploiement et la maintenance d'applications dans différents domaines. En parallèle, ces applications évoluent en continu pour garantir une bonne qualité de service et deviennent de plus en plus complexes. Cette évolution implique souvent des coûts de développement et de maintenance de plus en plus importants, auxquels peut s'ajouter une augmentation des coûts de déploiement sur des infrastructures d'exécution récentes comme le cloud. Réduire ces coûts et améliorer la qualité de ces applications sont actuellement des objectifs centraux du domaine du génie logiciel. Récemment, les microservices sont apparus comme un exemple de technologie ou style architectural favorisant l'atteinte de ces objectifs.Alors que les microservices peuvent être utilisés pour développer de nouvelles applications, il existe des applications monolithiques (i.e., monolithes) cons-truites comme une seule unité et que les propriétaires (e.g., entreprise, etc.) souhaitent maintenir et déployer sur le cloud. Dans ce cas, il est fréquent d'envisager de redévelopper ces applications à partir de rien ou d'envisager une migration vers de nouveaux styles architecturaux. Redévelopper une application ou réaliser une migration manuellement peut devenir rapidement une tâche longue, source d'erreurs et très coûteuse. Une migration automatique apparaît donc comme une solution évidente.L'objectif principal de notre thèse est de contribuer à proposer des solutions pour l'automatisation du processus de migration d'applications monolithiques orientées objet vers des microservices. Cette migration implique deux étapes : l'identification de microservices et le packaging de ces microservices. Nous nous focalisons sur d'identification en s'appuyant sur une analyse du code source. Nous proposons en particulier deux approches.La première consiste à identifier des microservices en analysant les relations structurelles entre les classes du code source ainsi que les accès aux données persistantes. Dans cette approche, nous prenons aussi en compte les recommandations d'un architecte logiciel. L'originalité de ce travail peut être vue sous trois aspects. Tout d'abord, les microservices sont identifiés en se basant sur l'évaluation d'une fonction bien définie mesurant leur qualité. Cette fonction repose sur des métriques reflétant la "sémantique" du concept "microservice". Deuxièmement, les recommandations de l'architecte logiciel ne sont exploitées que lorsqu'elles sont disponibles. Enfin, deux modèles algorithmiques ont été utilisés pour partitionner les classes d'une application orientée objet en microservices : un algorithme de regroupement hiérarchique et un algorithme génétique.La deuxième approche consiste à extraire à partir d'un code source orienté objet un workflow qui peut être utilisé en entrée de certaines approches existantes d'identification des microservices. Un workflow décrit le séquencement de tâches constituant une application suivant deux formalismes: un flot de contrôle et/ou un flot de données. L'extraction d'un workflow à partir d'un code source nécessite d'être capable de définir une correspondance entre les concepts du mon-de objet et ceux d'un workflow.Pour valider nos deux approches, nous avons implémenté deux prototypes et mené des expérimentations sur plusieurs cas d'étude. Les microservices identifiés ont été évalués qualitativement et quantitativement. Les workflows obtenus ont été évalués manuellement sur un jeu de tests. Les résultats obtenus montrent respectivement la pertinence des microservices identifiés et l'exactitude des workflows obtenusSoftware technologies are constantly evolving to facilitate the development, deployment, and maintenance of applications in different areas. In parallel, these applications evolve continuously to guarantee an adequate quality of service, and they become more and more complex. Such evolution often involves increased development and maintenance costs, that can become even higher when these applications are deployed in recent execution infrastructures such as the cloud. Nowadays, reducing these costs and improving the quality of applications are main objectives of software engineering. Recently, microservices have emerged as an example of a technology or architectural style that helps to achieve these objectives.While microservices can be used to develop new applications, there are monolithic ones (i.e., monoliths) built as a single unit and their owners (e.g., companies, etc.) want to maintain and deploy them in the cloud. In this case, it is common to consider rewriting these applications from scratch or migrating them towards recent architectural styles. Rewriting an application or migrating it manually can quickly become a long, error-prone, and expensive task. An automatic migration appears as an evident solution.The ultimate aim of our dissertation is contributing to automate the migration of monolithic Object-Oriented (OO) applications to microservices. This migration consists of two steps: microservice identification and microservice packaging. We focus on microservice identification based on source code analysis. Specifically, we propose two approaches.The first one identifies microservices from the source code of a monolithic OO application relying on code structure, data accesses, and software architect recommendations. The originality of our approach can be viewed from three aspects. Firstly, microservices are identified based on the evaluation of a well-defined function measuring their quality. This function relies on metrics reflecting the "semantics" of the concept "microservice". Secondly, software architect recommendations are exploited only when they are available. Finally, two algorithmic models have been used to partition the classes of an OO application into microservices: clustering and genetic algorithms.The second approach extracts from an OO source code a workflow that can be used as an input of some existing microservice identification approaches. A workflow describes the sequencing of tasks constituting an application according to two formalisms: control flow and /or data flow. Extracting a workflow from source code requires the ability to map OO conceptsinto workflow ones.To validate both approaches, we implemented two prototypes and conducted experiments on several case studies. The identified microservices have been evaluated qualitatively and quantitatively. The extracted workflows have been manually evaluated relying on test suites. The obtained results show respectively the relevance of the identified microservices and the correctness of the extracted workflows
6
Braun, Eric [Verfasser]. "Microservice-based Reference Architecture for Semantics-aware Measurement Systems / Eric Braun." Karlsruhe : KIT-Bibliothek, 2020. http://d-nb.info/1222109514/34.
Повний текст джерела
7
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.
Повний текст джерелаАнотація:
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.
8
Nhat, Minh Pham. "A proposal for a cloud-based microservice architecture for the Skolrutiner system." Thesis, Uppsala universitet, Institutionen för informationsteknologi, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-428348.
Повний текст джерелаАнотація:
Skolrutiner, a fast-moving startup company, has a great idea of aplatform for handling documents. However, they do not have a scalableand modular system architecture since all the current services arecentralized and running on a single virtual machine. The main purposeof this thesis is to study and design a cloud-based microservicesystem for the platform of the company. This new microserviceapproach, with the help of many modern features of cloud computing,is expected to resolve the major issues of the current system. Theproposed architecture might be costly and challenging to implement,but it could help the company to have a general knowledge about cloudcomputing, microservices, and how to apply these technologies to theexpanding business. The re-implementation of the Skolrutiner systembased on the given architecture is out of the scope of this thesiswork.
9
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.
Повний текст джерелаАнотація:
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.
10
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.
Повний текст джерелаАнотація:
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.
Книги з теми "Architecture à base de microservices"
1
Oliveira Rocha, Hugo Filipe. Practical Event-Driven Microservices Architecture. Berkeley, CA: Apress, 2022. http://dx.doi.org/10.1007/978-1-4842-7468-2.
Повний текст джерела
2
Building Microservices: Designing Fine-Grained Systems. Sebastopol, USA: O'Reilly Media, 2015.
Знайти повний текст джерела
3
Hogan, Rex. A practical guide to data base design. Englewood Cliffs, N.J: Prentice Hall, 1990.
Знайти повний текст джерела
4
Tanenbaum, Andrew S. Architecture de l'ordinateur: Du circuit logique au logiciel de base. Paris: InterEditions, 1988.
Знайти повний текст джерела
5
Blanchet, Gérard. Architecture des ordinateurs des techniques de base aux techniques avancées. Paris: Masson, 1991.
Знайти повний текст джерела
6
Tanenbaum, Andrew S. Architecture de l'ordinateur: Du circuit logique au logiciel de base. Paris: InterÉditions, 1987.
Знайти повний текст джерела
7
Malamud, Carl. Ingres: Tools for building an information architecture. New York: Van Nostrand Reinhold, 1989.
Знайти повний текст джерела
8
Kordjamshidi, Maria. House rating schemes: From energy to comfort base. Berlin: Springer, 2011.
Знайти повний текст джерела
9
Godse, Gopal Vinayak. Qutub Minar is Vishnu dhwaja: The lotus based Vishnudhwaja on the base of vastushastra : a scientific survey. Delhi: Surya Bharti Prakashan, 1997.
Знайти повний текст джерела
10
Mockridge, Patricia. Weathervanes. Princes Risborough: Shire Publications, 1993.
Знайти повний текст джерелаЧастини книг з теми "Architecture à base de microservices"
1
Christudas, Binildas. "Axon Microservices and BASE Transactions." In Practical Microservices Architectural Patterns, 779–812. Berkeley, CA: Apress, 2019. http://dx.doi.org/10.1007/978-1-4842-4501-9_19.
Повний текст джерела
2
Boyer, Fabienne, Xavier Etchevers, Noel de Palma, and Xinxiu Tao. "Architecture-Based Automated Updates of Distributed Microservices." In Service-Oriented Computing, 21–36. Cham: Springer International Publishing, 2018. http://dx.doi.org/10.1007/978-3-030-03596-9_2.
Повний текст джерела
3
Solarte, Zeida, Juan D. Gonzalez, Lyda Peña, and Oscar H. Mondragon. "Microservices-Based Architecture for Resilient Cities Applications." In Lecture Notes in Electrical Engineering, 423–32. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-53021-1_43.
Повний текст джерела
4
Gidey, Habtom Kahsay, Mario Kesseler, Patrick Stangl, Peter Hillmann, and Andreas Karcher. "Document-Based Knowledge Discovery with Microservices Architecture." In Communications in Computer and Information Science, 146–61. Cham: Springer International Publishing, 2022. http://dx.doi.org/10.1007/978-3-031-08277-1_13.
Повний текст джерела
5
Bandara, Eranga, Xueping Liang, Peter Foytik, Sachin Shetty, Nalin Ranasinghe, Kasun De Zoysa, and Wee Keong Ng. "SaaS - Microservices-Based Scalable Smart Contract Architecture." In Communications in Computer and Information Science, 228–43. Singapore: Springer Singapore, 2021. http://dx.doi.org/10.1007/978-981-16-0422-5_16.
Повний текст джерела
6
Nunes, Luís, Nuno Santos, and António Rito Silva. "From a Monolith to a Microservices Architecture: An Approach Based on Transactional Contexts." In Software Architecture, 37–52. Cham: Springer International Publishing, 2019. http://dx.doi.org/10.1007/978-3-030-29983-5_3.
Повний текст джерела
7
Maamouri, Amine, Lilia Sfaxi, and Riadh Robbana. "Phi: A Generic Microservices-Based Big Data Architecture." In Information Systems, 3–16. Cham: Springer International Publishing, 2022. http://dx.doi.org/10.1007/978-3-030-95947-0_1.
Повний текст джерела
8
Baran, Remigiusz, Pavol Partila, and Rafał Wilk. "Microservices Architecture for Content-Based Indexing of Video Shots." In Cryptology and Network Security, 444–56. Cham: Springer International Publishing, 2018. http://dx.doi.org/10.1007/978-3-319-98678-4_45.
Повний текст джерела
9
Moussa, Mohammed, Abdelhalim Benachenhou, Smail Belghit, Abderrahmane Adda Benattia, and Abderrahmane Boumehdi. "An Implementation of Microservices Based Architecture for Remote Laboratories." In Cross Reality and Data Science in Engineering, 154–61. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-52575-0_12.
Повний текст джерела
10
Singh, Amandeep, Vinay Raj, and Sadam Ravichandra. "Integration of Attribute-Based Access Control in Microservices Architecture." In ICT Systems and Sustainability, 681–90. Singapore: Springer Singapore, 2022. http://dx.doi.org/10.1007/978-981-16-5987-4_69.
Повний текст джерелаТези доповідей конференцій з теми "Architecture à base de microservices"
1
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.
Повний текст джерелаАнотація:
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.
2
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.
Повний текст джерелаАнотація:
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.
3
Dontsov, A. A., and I. A. Sutorikhin. "Development of a geographic information system for data collection and analysis based on microservice architecture." In Spatial Data Processing for Monitoring of Natural and Anthropogenic Processes 2021. Crossref, 2021. http://dx.doi.org/10.25743/sdm.2021.93.41.034.
Повний текст джерелаАнотація:
The paper discusses the use of microservice architecture in the development of geographic information systems (GIS) for collecting, processing and analyzing data. As a rule, microservice architecture is used to build applications in information systems related to solving business problems, and is not widespread in the development of geographic information systems in the scientific field. However, its application is now becoming increasingly important. Decomposition of the software implementation and GIS infrastructure associated with computations and data processing into components in the form of microservices has a number of advantages, such as: increased fault tolerance, increased flexibility, reduced maintenance effort, simplified scaling, and others. The first results of the application of the microservice approach in the development of a geoinformation system for the collection and processing of hydrological and hydrobiological data on the state of water bodies are shown. The architecture, main components, and features of the information infrastructure are shown.
4
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.
Повний текст джерелаАнотація:
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.
5
Aderaldo, Carlos M., Nabor C. Mendonca, Claus Pahl, and Pooyan Jamshidi. "Benchmark Requirements for Microservices Architecture Research." In 2017 IEEE/ACM 1st International Workshop on Establishing the Community-Wide Infrastructure for Architecture-Based Software Engineering (ECASE). IEEE, 2017. http://dx.doi.org/10.1109/ecase.2017.4.
Повний текст джерела
6
Bakshi, Kapil. "Microservices-based software architecture and approaches." In 2017 IEEE Aerospace Conference. IEEE, 2017. http://dx.doi.org/10.1109/aero.2017.7943959.
Повний текст джерела
7
de Camargo, André, Ivan Salvadori, Ronaldo dos Santos Mello, and Frank Siqueira. "An architecture to automate performance tests on microservices." In iiWAS '16: 18th International Conference on Information Integration and Web-based Applications and Services. New York, NY, USA: ACM, 2016. http://dx.doi.org/10.1145/3011141.3011179.
Повний текст джерела
8
Márquez, Gastón, Mónica M. Villegas, and Hernán Astudillo. "A pattern language for scalable microservices-based systems." In ECSA '18: 12th European Conference on Software Architecture. New York, NY, USA: ACM, 2018. http://dx.doi.org/10.1145/3241403.3241429.
Повний текст джерела
9
Mathai, Alex, Sambaran Bandyopadhyay, Utkarsh Desai, and Srikanth Tamilselvam. "Monolith to Microservices: Representing Application Software through Heterogeneous Graph Neural Network." In Thirty-First International Joint Conference on Artificial Intelligence {IJCAI-22}. California: International Joint Conferences on Artificial Intelligence Organization, 2022. http://dx.doi.org/10.24963/ijcai.2022/542.
Повний текст джерелаАнотація:
Monolithic software encapsulates all functional capabilities into a single deployable unit. But managing it becomes harder as the demand for new functionalities grow. Microservice architecture is seen as an alternative as it advocates building an application through a set of loosely coupled small services wherein each service owns a single functional responsibility. But the challenges associated with the separation of functional modules, slows down the migration of a monolithic code into microservices. In this work, we propose a representation learning based solution to tackle this problem. We use a heterogeneous graph to jointly represent software artifacts (like programs and resources) and the different relationships they share (function calls, inheritance, etc.), and perform a constraint-based clustering through a novel heterogeneous graph neural network. Experimental studies show that our approach is effective on monoliths of different types.
10
Orduz, Juan S., Gabriel D. Orozco, Carlos H. Tobar-Arteaga та Oscar Mauricio Caicedo Rendon. "μvIMS: A Finer-Scalable Architecture Based on Microservices". У 2019 IEEE 44th LCN Symposium on Emerging Topics in Networking (LCN Symposium). IEEE, 2019. http://dx.doi.org/10.1109/lcnsymposium47956.2019.9000664.
Повний текст джерелаЗвіти організацій з теми "Architecture à base de microservices"
1
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.
Повний текст джерела
2
Krishnaswamy, M., and D. Romascanu. Management Information Base for the PINT Services Architecture. RFC Editor, February 2001. http://dx.doi.org/10.17487/rfc3055.
Повний текст джерела
3
Baker, F., K. Chan, and A. Smith. Management Information Base for the Differentiated Services Architecture. RFC Editor, May 2002. http://dx.doi.org/10.17487/rfc3289.
Повний текст джерела
4
Roboam, Michel, Mark S. Fox, and Katia Sycara. Enterprise Management Network Architecture Distributed Knowledge Base Support. Fort Belvoir, VA: Defense Technical Information Center, November 1990. http://dx.doi.org/10.21236/ada230113.
Повний текст джерела
5
Combs, V., J. Hanna, J. Bryant, B. Lipa, S. Tucker, T. Krokowski, J. Reilly, and G. Hasseler. Phoenix: Service Oriented Architecture for Information Management - Base Implementation Document. Fort Belvoir, VA: Defense Technical Information Center, September 2011. http://dx.doi.org/10.21236/ada549822.
Повний текст джерела
6
NAVAL OCEAN SYSTEMS CENTER SAN DIEGO CA. Base Exterior Architecture Plan: Naval Ocean Systems Center Hawaii Laboratory, Oahu, Hawaii. Fort Belvoir, VA: Defense Technical Information Center, February 1990. http://dx.doi.org/10.21236/ada222632.
Повний текст джерела
7
Caté, A., P. Mercier-Langevin, P. S. Ross, S. Duff, M D Hannington, B. Dubé, and S. Gagné. The Paleoproterozoic Lalor VMS deposit, Snow Lake, Manitoba: observations on the nature and architecture of the gold and base metal-rich ore zones and associated alterations. Natural Resources Canada/ESS/Scientific and Technical Publishing Services, 2014. http://dx.doi.org/10.4095/293116.
Повний текст джерела
8
Cunningham, Stuart, Marion McCutcheon, Greg Hearn, Mark Ryan, and Christy Collis. Australian Cultural and Creative Activity: A Population and Hotspot Analysis: Sunshine Coast. Queensland University of Technology, December 2020. http://dx.doi.org/10.5204/rep.eprints.136822.
Повний текст джерелаАнотація:
The Sunshine Coast (unless otherwise specified, Sunshine Coast refers to the region which includes both Sunshine Coast and Noosa council areas) is a classic regional hotspot. In many respects, the Sunshine Coast has assets that make it the “Goldilocks” of Queensland hotspots: “the agility of the region and our collaborative nature is facilitated by the fact that we're not too big, not too small - 330,000 people” (Paddenburg, 2019); “We are in that perfect little bubble of just right of about everything” (Erbacher 2019). The Sunshine Coast has one of the fastest-growing economies in Australia. Its population is booming and its local governments are working together to establish world-class communications, transport and health infrastructure, while maintaining the integrity of the region’s much-lauded environment and lifestyle. As a result, the Sunshine Coast Council is regarded as a pioneer on smart city initiatives, while Noosa Shire Council has built a reputation for prioritising sustainable development. The region’s creative economy is growing at a faster rate that of the rest of the economy—in terms of job growth, earnings, incomes and business registrations. These gains, however, are not spread uniformly. Creative Services (that is, the advertising and marketing, architecture and design, and software and digital content sectors) are flourishing, while Cultural Production (music and performing arts, publishing and visual arts) is variable, with visual and performing arts growing while film, television and radio and publishing have low or no growth. The spirit of entrepreneurialism amongst many creatives in the Sunshine Coast was similar to what we witnessed in other hotspots: a spirit of not necessarily relying on institutions, seeking out alternative income sources, and leveraging networks. How public agencies can better harness that energy and entrepreneurialism could be a focus for ongoing strategy. There does seem to be a lower level of arts and culture funding going into the Sunshine Coast from governments than its population base and cultural and creative energy might suggest. Federal and state arts funding programs are under-delivering to the Sunshine Coast.
9
Weller, Joel I., Derek M. Bickhart, Micha Ron, Eyal Seroussi, George Liu, and George R. Wiggans. Determination of actual polymorphisms responsible for economic trait variation in dairy cattle. United States Department of Agriculture, January 2015. http://dx.doi.org/10.32747/2015.7600017.bard.
Повний текст джерелаАнотація:
The project’s general objectives were to determine specific polymorphisms at the DNA level responsible for observed quantitative trait loci (QTLs) and to estimate their effects, frequencies, and selection potential in the Holstein dairy cattle breed. The specific objectives were to (1) localize the causative polymorphisms to small chromosomal segments based on analysis of 52 U.S. Holstein bulls each with at least 100 sons with high-reliability genetic evaluations using the a posteriori granddaughter design; (2) sequence the complete genomes of at least 40 of those bulls to 20 coverage; (3) determine causative polymorphisms based on concordance between the bulls’ genotypes for specific polymorphisms and their status for a QTL; (4) validate putative quantitative trait variants by genotyping a sample of Israeli Holstein cows; and (5) perform gene expression analysis using statistical methodologies, including determination of signatures of selection, based on somatic cells of cows that are homozygous for contrasting quantitative trait variants; and (6) analyze genes with putative quantitative trait variants using data mining techniques. Current methods for genomic evaluation are based on population-wide linkage disequilibrium between markers and actual alleles that affect traits of interest. Those methods have approximately doubled the rate of genetic gain for most traits in the U.S. Holstein population. With determination of causative polymorphisms, increasing the accuracy of genomic evaluations should be possible by including those genotypes as fixed effects in the analysis models. Determination of causative polymorphisms should also yield useful information on gene function and genetic architecture of complex traits. Concordance between QTL genotype as determined by the a posteriori granddaughter design and marker genotype was determined for 30 trait-by-chromosomal segment effects that are segregating in the U.S. Holstein population; a probability of <10²⁰ was used to accept the null hypothesis that no segregating gene within the chromosomal segment was affecting the trait. Genotypes for 83 grandsires and 17,217 sons were determined by either complete sequence or imputation for 3,148,506 polymorphisms across the entire genome. Variant sites were identified from previous studies (such as the 1000 Bull Genomes Project) and from DNA sequencing of bulls unique to this project, which is one of the largest marker variant surveys conducted for the Holstein breed of cattle. Effects for stature on chromosome 11, daughter pregnancy rate on chromosome 18, and protein percentage on chromosome 20 met 3 criteria: (1) complete or nearly complete concordance, (2) nominal significance of the polymorphism effect after correction for all other polymorphisms, and (3) marker coefficient of determination >40% of total multiple-regression coefficient of determination for the 30 polymorphisms with highest concordance. The missense polymorphism Phe279Tyr in GHR at 31,909,478 base pairs on chromosome 20 was confirmed as the causative mutation for fat and protein concentration. For effect on fat percentage, 12 additional missensepolymorphisms on chromosome 14 were found that had nearly complete concordance with the suggested causative polymorphism (missense mutation Ala232Glu in DGAT1). The markers used in routine U.S. genomic evaluations were increased from 60,000 to 80,000 by adding markers for known QTLs and markers detected in BARD and other research projects. Objectives 1 and 2 were completely accomplished, and objective 3 was partially accomplished. Because no new clear-cut causative polymorphisms were discovered, objectives 4 through 6 were not completed.
10
Lewis, Dustin, Radhika Kapoor, and Naz Modirzadeh. Advancing Humanitarian Commitments in Connection with Countering Terrorism: Exploring a Foundational Reframing concerning the Security Council. Harvard Law School Program on International Law and Armed Conflict, December 2021. http://dx.doi.org/10.54813/uzav2714.
Повний текст джерелаАнотація:
The imperative to provide humanitarian and medical services on an urgent basis in armed conflicts is anchored in moral tenets, shared values, and international rules. States spend tens of billions of dollars each year to help implement humanitarian programs in conflicts across the world. Yet, in practice, counterterrorism objectives increasingly prevail over humanitarian concerns, often resulting in devastating effects for civilian populations in need of aid and protection in war. Not least, confusion and misapprehensions about the power and authority of States relative to the United Nations Security Council to set policy preferences and configure legal obligations contribute significantly to this trajectory. In this guide for States, we present a framework to reconfigure relations between these core commitments by assessing the counterterrorism architecture through the lens of impartial humanitarianism. We aim in particular to provide an evidence base and analytical frame for States to better grasp key legal and policy issues related to upholding respect for principled humanitarian action in connection with carrying out the Security Council’s counterterrorism decisions. We do so because the lack of knowledge regarding interpretation and implementation of counterterrorism resolutions matters for the coherence, integrity, and comprehensiveness of humanitarian policymaking and protection of the humanitarian imperative. In addition to analyzing foundational concerns and evaluating discernible behaviors and attitudes, we identify avenues that States may take to help achieve pro-humanitarian objectives. We also endeavor to help disseminate indications of, and catalyze, States’ legally relevant positions and practices on these issues. In section 1, we introduce the guide’s impetus, objectives, target audience, and structure. We also describe the methods that we relied on and articulate definitions for key terms. In section 2, we introduce key legal actors, sources of law, and the notion of international legal responsibility, as well as the relations between international and national law. Notably, Security Council resolutions require incorporation into national law in order to become effective and enforceable by internal administrative and judicial authorities. In section 3, we explain international legal rules relevant to advancing the humanitarian imperative and upholding respect for principled humanitarian action, and we sketch the corresponding roles of humanitarian policies, programs, and donor practices. International humanitarian law (IHL) seeks to ensure — for people who are not, or are no longer, actively participating in hostilities and whose needs are unmet — certain essential supplies, as well as medical care and attention for the wounded and sick. States have also developed and implemented a range of humanitarian policy frameworks to administer principled humanitarian action effectively. Further, States may rely on a number of channels to hold other international actors to account for safeguarding the humanitarian imperative. In section 4, we set out key theoretical and doctrinal elements related to accepting and carrying out the Security Council’s decisions. Decisions of the Security Council may contain (binding) obligations, (non-binding) recommendations, or a combination of the two. UN members are obliged to carry out the Council’s decisions. Member States retain considerable interpretive latitude to implement counterterrorism resolutions. With respect to advancing the humanitarian imperative, we argue that IHL should represent a legal floor for interpreting the Security Council’s decisions and recommendations. In section 5, we describe relevant conduct of the Security Council and States. Under the Resolution 1267 (1999), Resolution 1989 (2011), and Resolution 2253 (2015) line of resolutions, the Security Council has established targeted sanctions as counterterrorism measures. Under the Resolution 1373 (2001) line of resolutions, the Security Council has adopted quasi-“legislative” requirements for how States must counter terrorism in their national systems. Implementation of these sets of resolutions may adversely affect principled humanitarian action in several ways. Meanwhile, for its part, the Security Council has sought to restrict the margin of appreciation of States to determine how to implement these decisions. Yet international law does not demand that these resolutions be interpreted and implemented at the national level by elevating security rationales over policy preferences for principled humanitarian action. Indeed, not least where other fields of international law, such as IHL, may be implicated, States retain significant discretion to interpret and implement these counterterrorism decisions in a manner that advances the humanitarian imperative. States have espoused a range of views on the intersections between safeguarding principled humanitarian action and countering terrorism. Some voice robust support for such action in relation to counterterrorism contexts. A handful call for a “balancing” of the concerns. And some frame respect for the humanitarian imperative in terms of not contradicting counterterrorism objectives. In terms of measures, we identify five categories of potentially relevant national counterterrorism approaches: measures to prevent and suppress support to the people and entities involved in terrorist acts; actions to implement targeted sanctions; measures to prevent and suppress the financing of terrorism; measures to prohibit or restrict terrorism-related travel; and measures that criminalize or impede medical care. Further, through a number of “control dials” that we detect, States calibrate the functional relations between respect for principled humanitarian action and countering terrorism. The bulk of the identified counterterrorism measures and related “control dials” suggests that, to date, States have by and large not prioritized advancing respect for the humanitarian imperative at the national level. Finally, in section 6, we conclude by enumerating core questions that a State may answer to help formulate and instantiate its values, policy commitments, and legal positions to secure respect for principled humanitarian action in relation to counterterrorism contexts.