6 research outputs found
A Systematic Mapping Study in Microservice Architecture
The accelerating progress of network speed, reliability and security creates an increasing demand to move software and services from being stored and processed locally on users' machines to being managed by third parties that are accessible through the network. This has created the need to develop new software development methods and software architectural styles that meet these new demands. One such example in software architectural design is the recent emergence of the microservices architecture to address the maintenance and scalability demands of online service providers. As microservice architecture is a new research area, the need for a systematic mapping study is crucial in order to summarise the progress so far and identify the gaps and requirements for future studies. In this paper we present a systematic mapping study of microservices architectures and their implementation. Our study focuses on identifying architectural challenges, the architectural diagrams/views and quality attributes related to microsevice systems
Supporting Migration to Microservices with Domain Driven Design
Uma empresa e-commerce com um marketplace disponĂvel para todo o mundo tem crescido significativamente durante os anos, com mais clientes interessados e um aumento nas vendas. Com isto, o software cresceu com a tendĂȘncia, numa arquitetura a nĂvel monolĂtica. A ĂĄrea de processamento de encomendas foi a que se mais sentiu este aumento, com um serviço monolĂtico que integra mĂșltiplas equipas de desenvolvimento com Ăąmbitos de negĂłcio abrangentes. A equipa apelidada de âSTâ Ă© uma das participantes, tendo como responsabilidades, a implementação e manutenção do software para OcorrĂȘncias em Encomendas e DevoluçÔes. No entanto, para a equipa âSTâ Ă© cada vez mais complicado realizar alteraçÔes no seu software, visto que o domĂnio nĂŁo Ă© mais flexĂvel, sendo uma tarefa difĂcil para os programadores, a sua compreensĂŁo e a sua evolução para novos requisitos de negĂłcio. Aproveitando a tendĂȘncia de evolução existente na plataforma, a equipa âSTâ realizarĂĄ uma migração do software de OcorrĂȘncias para uma arquitetura orientada a microserviços, com auxĂlio de Domain Driven Design, definindo os contextos limitados, desenhando os modelos de domĂnio, e implementando os respetivos serviços com a utilização de boas prĂĄticas de engenharia, como padrĂ”es de software. No final, os programadores da equipa âSTâ com o auxĂlio dos seus conhecimentos, serĂŁo os responsĂĄveis por fazer uma avaliação final da solução, de forma a perceber se esta mitigou os constrangimentos que causavam o problema enunciado.An e-commerce company with a marketplace available for all over the world has grown significantly over the years, having more interested customers increasing its sales. With this, software tended to expand in a monolithic way. The order processing is one of the areas that grew the most, with a monolithic service that integrates multiple development teams with business broad scopes. The team called âSTâ is one of the participants, having the responsibility of implementing and maintain the software related to Order and Return Occurrences. However, for the âSTâ team developers is increasingly difficult to change its software, since the domain is not flexible anymore, being a tough task for developers, its understanding and its evolution for new business requirements. Taking advantage of the evolution trend, existent on the platform, the âSTâ will migrate the Occurrences software to a microservices oriented architecture, with the Domain Driven Design support, delineating its bounded contexts, drawing its domain models, and implementing the corresponding services with usage of good engineering practices, such as software patterns. Finally, the âSTâ team developers, supported by their knowledge, are the responsible ones to evaluate the final implemented solution, in order to understand if it mitigates the constraints that caused the announced problem
Komponenttipohjaisen micro frontend -arkkitehtuurin suunnittelu : tapaus Visma Tampuuri Oy:n Asukassivut
Micro frontend -arkkitehtuuri on mikropalveluarkkitehtuurin erikoistapaus, jossa mikropalveluiden rooliin kuuluu tuottaa datan lisÀksi myös kÀyttöliittymÀ toimintoineen. Toistaiseksi tÀstÀ arkkitehtuurimallista on julkaistu kirjallisuutta varsin vÀhÀn ja esitetyt mallit ovat enimmÀkseen prototyyppitoteutuksia.
TÀssÀ tutkielmassa tarkastellaan erÀÀn tietyn ohjelmistoprojektin tuloksena syntynyttÀ micro frontend -ratkaisua design science -kehyksessÀ. Aluksi kuvataan toimintaympÀristö, ongelmat ja sieltÀ nousevat vaatimukset. TÀhÀn esitetÀÀn Web Components -teknologiaan perustuva ratkaisu, jonka kelpoisuutta arvioidaan sekÀ sen tuotantokÀytöstÀ saatujen kokemusten perusteella ettÀ ATAM-evaluointimenetelmÀÀ kÀyttÀen.
Saadut tulokset osoittavat muun muassa sen, ettĂ€ edellĂ€ mainittu Web Components -teknologia mahdollistaa HTML-standardin mÀÀrittelemien ohjelmointirajapintojen suoran ja tehokkaan kĂ€ytön web-kehityksessĂ€ â ilman tarvetta ohjelmistokehyksille. LisĂ€ksi kyseenalaistetaan nĂ€kemys, jonka mukaan micro frontend -arkkitehtuurin kehitys olisi jĂ€rkevÀÀ vain organisatorisista syistĂ€: sille voi olla myös vahvat perustelut esimerkiksi ohjelmiston muokattavuudelle asetettujen vaatimusten vuoksi, ja se on mahdollista toteuttaa myös pienen kehittĂ€jĂ€ryhmĂ€n toimesta