Microservices

In this post, I will discuss the article: "Microservices: a definition of this new architectural term", written by y James Lewis and Martin Fowler.

First, it is important to understand what the term "Microservice Architecture" means, a microservice architectural style is an approach to developing a single application as a suite of small services, each running in its own process and communicating each other. These services are built around business capabilities and are independently deployable.
Microservices have a great advantage over a monolithic application,because this style does not put all the functionality into a single process, and  if you want to make a change you do not need to rebuild the application.
This article and this term, reminds me of the activity we had in the first class of the subject Software Design and Architecture, where we reflect on the concept an importance of modules and components using Lego blocks.

The microservices must exhibit certain characteristics, in order to fulfill their function, they must be un-automated components, automated, organized around business capabilities, focused on the construction of products. And again! simplicity is important, making the architecture simple is good for everyone involved in software development. Having microservices makes it easier for the team to make changes and extend the functionalities of an application, and also makes it easier to solve problems and achieve goals in a satisfactory way. 
 
The use of microservices has turned out so well that more and more companies are beginning to adopt this style of architecture, although it is not a very mature area, it has great potential because it covers many of the deficiencies of the monolithic architecture approach. It is clear that you can not immediately move a monolithic system to one with microservices, the authors give good advice: start with a monolith, keep it modular, and split it into microservices once the monolith becomes a problem. Microservices are now a key and a big difference in an architecture of an efficient system.
It seems to me that microservices will help to build the future.
 

Comentarios

Publicar un comentario

Entradas populares de este blog

Software Craftsmanship

Imagen
I n this post, I will discuss the podcast: "Software Craftsmanship", with Bob Martin (Uncle Bob) produced by Software Engineering Radio in 2009. This podcast is about agile software development and software craftsmanship. This podcast reminded me of two past posts on this blog,  one called Is Design Dead?  and the other called Who needs an architect? In which the role of the software architect is largely discussed, and also agile design and methods. The first idea that I think it is important to mention and that I also support is that  Uncle Bob  thinks that software architects should not stop programming, because the separation of the leaders and the developers, concludes in bad decisions that can complicate the projects, it is important that they keep their fingers on the keyboard, in this way they understand better the problems that arise and can better lead a team and carry out more complex designs. Robert explains in the podcast what is the software Craftmans
Leer más

Who Needs an Architect?

Imagen
I n this post, I will discuss the article: "Who needs an architect? " , written by Martin Fowler. In the last entry we defined the software architecture as a high-level design, the IEEE definition also defines architecture as “the highest level concept of a system in its environment. The architecture of a software system is its organization or structure of significant components interacting through interfaces".  It seems that Martin Fowler and many other people do not agree with his definition, like Ralph Johnson, who tells us there's no highest level concept of a system. The best definition they propose is the following:“In most successful software projects, the expert developers working on that project have a shared understanding of the system design. This shared understanding is called ‘ architecture. ’ This understanding includes how the system is divided into components and how the components interact through interfaces.” Sounds better to me, because
Leer más