Microservices

Today I will talk about the article “Microservices” by James Lewis and Martin Fowler (March, 2014). This term is used to refer to a way of designing software in small independent services that will work together. This is used mainly in business applications and has some peculiar characteristics.
    In other words 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 with 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.
    Of the most interesting things that this design pattern has is that each microservice can be seen as a black box, and thus remove a bit of the complexity of our system. What I like the most about considering each microservice as a black box is that you can not worry about the programming language and only focus on your microservice functioning correctly.
    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,to do this we will first start with a monolith, then 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 and I think microservices will help to build the future.

Comentarios

Publicar un comentario

Entradas populares de este blog

Hidden Figures

Today I will talk about the amazing movie titled “Hidden Figures”. Normally in those times they didn’t recognize all the women were part of important projects and this movie is one example of how they used to hide the work from the matchless Katherine Johnson. I can say that it has become one of my favorite movies.     The film tells the story of three African-American women who worked for NASA in the early 1960s, collaborating in an important space program. These brilliant women achieved incredible goals that seemed impossible because they were women and African-Americans.     What impresses me about these women is their intelligence, their strength, their perseverance and their struggle that allowed them to demonstrate that they were more than capable of being involved in areas that were considered suitable only for the masculine intellect, such as science, mathematics and engineering.     I can identify a little with those great women of that movie, not because of how brilliant t
Leer más

The 4+1 View Model

Today I will talk about the resources related to The 4+1 View Model, two Youtube videos and one article named The Elephant and the Blind Programmers by Grady Booch. These videos and article speak briefly about the 4 + 1 view model, this small model consists of four sections and an additional section that is part +1, which allows us to make a better software architecture. Let me explain these views: - Logical view: This view tells us what kind of objects we are going to build, how they communicate and what kind of data they are. - Development view: It is useful for developers to always know which part is related to what else and how things are organized during development. - Process view: describes the concurrency and synchronized aspects in the software and the process of using the software or doing things. - Physical view: It tells us how the software and the hardware are related. - Use cases or scenarios (+1): They are the explanation on how the system is expected to behave, w
Leer más

Understanding the SOLID Principles

Today I will talk about the Edward Guiness’ book section titled “Understanding the SOLID Principles”. First of all Solid is an acronym that stands for five principles of object-oriented programming and design. These principles help to avoid dependencies between the classes. S-Single Responsibility Principle O-Open/Closed Principle L-Liskov Substitution Principle I- Interface Segregation Principle D-Dependency Inversion Principle Talking a bit more of these principles we are going to explain each one: Single Responsibility Principle: This principle states that one class should only have one responsibility so the changes in that class do not end up affecting unrelated critical features on the system. This happens from a single action to a set of processes. You can take a view that a single responsibility refers to a group of related business processes. The stamina and tolerance determine how far you go Open/closed Principle: This principle talks about that classes should be op
Leer más