Microservices

Today's blog is about Microservices architectural style, this refers to the approach of developing a single application as a suite of small services. As I was reading the article I really understood that I did not know anything about Microservices, I had a bearly idea about it but I was on the lost path. The authors give some characteristics of microservices and I will list them.

*Componentization via Services
*Organized around Business Capabilities
*Product not Projects
*Smart endpoints and dumb pipes
*Decentralized Governance
*Decentralized Data Management
*Design for failure
*Infrastructure Automation
*Evoluionary Design

Every one of these explains to us what the Microservice should have, I will explain some of them. 

*Componentization via Services: Components will be set up into libraries that will be broken down into services.

*Design for failure: Software must tolerate the failure of the external services

*Smart endpoints and dumb pipes: Endpoints should take care of all the domain logic, receiving the request, applying logic as an appropiate and producing response. 

*Decentralized Governance: Programmers should take advantage of any tool they have, they should be able to code in any given language.

*Decentralized Data Management: Let each service manage its own database.

I understood these concepts but I think with the practice I will learn them even more, I hope there is some final project or homework-related with the topic. And knowing my professor I know he will do his best to explain to us this topic.














Comentarios

Publicar un comentario

Entradas más populares de este blog

WarGames

So Ernest Cline does an excellent job, building up the expectative in Ready Player One, about WarGames. The first time I heard about this movie was in the book Ready Player One, I did not understand the reference about this movie, it's supposed to be one of the favourites movies of one of the main characters. I was born in 1996 so this movie was a bit old for me. Being a guy who likes geek stuff this was so awesome for me.  A professor of mine who is one of the professors who teaches me compilers told the class that this movie was one of the main reasons for him and most of the people he knows to study a major related with computer science. So we were watching a piece of history. At first, I was so amazed to watch those old computers, they were so big and yet for the age so powerful. I was intrigued by how they have all this set up they need to have to program. But not only I was intrigued by the computers, but I also was surprised about how a 14-year-oldish boy can almost start
Leer más

Ethical Reflection on Ready Player One

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) I deeply agree with this quote, I believe that the world would hide its problems inside Oasis, we can see that the world it's collapsing when you see the conditions in which Parzival was living on, he was living in a kinda dump. I'd love to test the Oasis and see how VR has grown. For me VR it's an incredible technology we can take advantage of, currently, I'm taking a class of VR and I can say I'm really impressed how much it has grown, it's really like if you are in another world. Sometimes I forget where I am and nowadays VR it's not as developed as in Ready Player One, so I understand how easy it can get to lost in the game.  I
Leer más

Understanding the SOLID principles

These 5 principles are great advice discovered by Robert Martin also known as "Uncle Bob", the same we heard a podcast blog entrance ago. His acronym makes it easier for learning his principles, whenever we're developing object-oriented programs. The 5 principles are listed down below: S ingle Responsibility Principle (SRP): States that any class should have only one responsibility, although the author at some point says that there could be some classes that have 2 responsibilities. As the author continued with his explanation it confused me a little bit, because he contradicts himself. Maybe it could be clearer with the practice, as it's with all things in life.  O pen/Closed Principle (OPC): States that a class or a function should be open for extension but closed for modification. It attempts to counter the tendency for object-oriented code to become easy to be broken.  When adding new behaviour you need to leave alone the base classes instead you
Leer más