Microservices

-
After reading the article "Microservices", there are a few things that I would like to discuss, we must start first by defining what does a Microservice is. A Microservice architectural style is an approach to developing a single application into modules, each one running its own process and communicating with each other, so when an update is needed the process of implementing the changes is easier. 

One interesting thing is the way the Microservice style is compared to the monolithic style where a monolithic application is built as a single unit. A monolithic server is a natural way to approach building such a system. Explaining in a simple way, a monolithic application puts all its functionality into a single process and scales by replicating the monolith into multiple servers; while a microservice architecture puts each element of functionality into separate service and scales it by distributing these services across servers, replicating as needed. 

A Microservice has some characteristics, such as: 

- Uses libraries (components linked to a program and called using in-memory function calls) but their primary way of componentizing is by breaking down into services (out-of-process components who communicate with a mechanism such as a web service request or remote procedure call). 

- Split into services organized around business capability. 

- Prefers the notion that a team should own a product over its full lifetime, this means that the development is for products, not projects. There is a relationship where the question is how can software enhance business capability. 

- Decentralized Data Management. 

- Infrastructure Automation. 

- Designed for failure. 

- Evolutionary design. 

I consider that Microservice architecture has a lot of future since they are an excellent tool for every system os platform. I am sure that many of the big tech companies will be using Microservice architecture in the next 5 years or maybe they are currently using it to make they platforms stable for customers, supporting huge numbers of petitions to the platforms. I really enjoyed this reading and I am sure that if one day I have to implement a solution for a business I will use microservice architecture.

References: 

- Lewis, J., & Fowler, M. (2014, March). Microservices. Retrieved from https://martinfowler.com/articles/microservices.html

Comentarios

Publicar un comentario

Entradas más populares de este blog

Understanding the SOLID Principles

-
The following blog entry will explain the SOLID Principles based on the book Ace the programming interview: 160 questions and answers for success.  SOLID stands for 5 widely accepted principles of object-oriented programming and design, these are the S ingle Responsibility Principle, O pen/Closed Principle, L iskov Substitution Principle, I nterface Segregation Principle, D ependency Inversion Principle. These principles will be explained through this entry.  - Single Responsibility Principle: This principle says that a class should have only one responsibility. It should have only a reason or a class of reasons that cause it to change. This principle might cause a problem for programmers because deciding what a single responsibility means can be a difficulty. A single responsibility refers to a group of related business processes or it could be broken down in its constituent parts, with each part designated as a responsibility. - Open/Closed Principle: This principle s
Leer más

Ethical Reflection on Ready Player One

-
Everything that has a beginning must have an end and this book is not the exception. During the course of S/W Design and Architecture, we read the book "Ready Player One" by Ernest Cline and I would like to make an ethical reflection of this book through this blog entry. I would like to start with two quotes:  Morrow wrote in his autobiography that he’d left GSS because ... he felt that the OASIS had evolved into something horrible. “It had become a self-imposed prison for humanity,” he wrote. “A pleasant place for the world to hide from its problems while human civilization slowly collapses, primarily due to neglect.” (p. 120)  (Halliday speaking) “I created the OASIS because I never felt at home in the real world. I didn’t know how to connect with people there. I was afraid, for all of my life. Right up until I knew it was ending. That was when I realized, as terrifying and painful as reality can be, it’s also the only place where you can find true happiness. Beca
Leer más