Microservices

The microservices architecture is a recent term used for this new perspective for the software architecture, and it's based on getting several small services running into a single application that are communicating constantly with the computer via API using HTTP. This information may appear a little so technical but will get relevant at the time of understanding it's structure and purpose.

It may appear that is not that different for the traditional model of architectures like the libraries but the microservices get you benefits like the independence of the services, every service could be used and saving a lot of processing for each application opened. This independence also helps at the moment of creating efficient interfaces and to get explicitly the function of every service.

The changes in organization, and the approach changing from a project model to a product model, are also differentiators that makes interesting changes for the microservices perspective. Also I've found very interesting the idea decentralization for the governance and the data management, getting even more possibilities for organization and for getting each context independently.

The article mentions a lot of disadvantages also, but are refereed to being at the development, giving us more potential to grow and to get the evolve into rails. I find the benefits of using microservices way stronger that the disadvantages and I understand why this kind of architecture is getting time and time even more popular.

It's stated into the article that its not a certainty for the microservices to be the future, but I think that the last years this tendency has been spreading for the software projects that came to be successful. I get that it's impossible to change all the paradigm for the architectures, that's why getting us more perspective around the potential that has an innovative architecture it's so important and that's the reason for me to like this article.

Comentarios

Publicar un comentario

Entradas más populares de este blog

Is Design Dead?

For this article there is several topics that appeared very interesting to me. For the initial themes treated, one was the difference between the traditional structured design, and the evolutionary design, and it's a matter that I've even seen as a difficult topic because of the different perspectives presented even by my own teachers, some of them teaching me that the planned design is extremely important and even forcing this practices into our projects, but in the other perspective, some professors taught me to be evolutionary, and to make incremental design based on prototypes making really confusing the decision for the design every project I've made. Also, one of the things that I've found curious into the article is the association that the author makes between the refactoring and the YAGNI's simplicity to the evolutionary design. It's not that usual to understand the "best practices" of programming as supporting any bigger concept than the co
Leer más

The 4 + 1 Model

For this week we have several material to use, and I found it great. First the video that gets us the theory for the 4 different perspective model architecture plus 1, this part of the homework is connected to video that told us a story about the blind men who touched an elephant, and this two are necessary for fully understand the last article, getting combined into this new story about the programmers that found a new program thing and get to understand it in different ways. Its important to mention first the 4+1 model and each view of it, getting initialy the logical view explaining the behavior of components using state machine or sequence diagrams, the process view that gets the way of communication for the different system processes, also we got the development view that describes the elements and the components for the system in order to be completed, at last for the fourth view we got the physical view giving us the physical distribution for the components as well as the topo
Leer más