Microservices

In this blog, I will discuss the article titled "Microservices" written by James Lewis and Martin Fowler in March of 2014. I found the article to be interesting and shed some light to things I didn’t know about microservices.
Microservices are a type of architecture that structures applications as a bundle of different services. What's good about them is that they allow for continuous and efficient deployment of applications into complex systems. So their implementation is often vital when working on a problem that requires a large subset of tools and resources in order to work, meaning that this system is complex and big in size. What microservices accomplish is that it allows companies and different application services to widen their stack of technology and enable the continuous delivery and deployment of technologies into their systems.
Companies tend to apply microservices when their systems grow largely and become more complex. This allows the system to become, to some degree, self-sufficient and help to diminish their complexity in many ways.

Some examples of platforms that use microservices, or have at least evolved to a microservices architecture are: Netflix, Amazon, eBay, Bluemix, Soundcloud, amongst some of the many large web application that use this architecture. Some of the companies that made this changes are because the became monolithic in size and needed a way to make their systems less complex for the growth they were having.

Microservices are often implemented in teams where agile development is used. This is because their style of development couples nicely with the fastness of microservices implementation.
I’ved use microservices in smaller scales, not in big implementations where they most likely show the most profit. As it's said in the article, this architecture style is not for beginner programmers or people that are in bad coders. Because the style of changes could compromise some of the modules of the system.

Comentarios

Publicar un comentario

Entradas populares de este blog

Ready Player One

In this blog, I will discuss the book Ready Player One by Ernest Cline. We read this book during this course and I must say I really enjoyed reading it, so far its one of my favorite science fiction book. The book is about a dystopian future where society has abandoned reality and instead decided to live most of their lives inside a virtual reality simulation where everything is more “grandiose”. The story follows Wade Watts in his journey to find Hallidays (the creator of the game who past away) easter eggs, the person that finds all the easter eggs will inherit his vast fortune. I think there are many similarities with the virtual world in the book (OASIS) and the virtual world we currently have in our lives (social media, video games, mobile apps and other IT technologies). Because in the end, they are all outlets to escape our realities in some way. Our world is not dystopian like the one in the book, but we are living in an age where we want everything quick and easy. Tha...
Leer más

The 4+1 View Model

In this blog, I will discuss and review the videos called "4+1 View Into Software Architecture" and "Six Blind Men", as well as the article titled "The Elephant and the Blind Programmers" by Grady Booch written in 2010. Often times when developing, we don’t take into consideration the interactions users will have into our system and in doing so, we degrade the experience of what we build. The interaction can vary from user to user. That's what we see in the video where the blind men interact with the elephant. Their interpretation of what that elephant is like varies because of their different perspectives and because they chose different parts of the elephant to make that judgement. And that's all good, because having a different interpretation doesn’t mean they are wrong. Because the combination of their interpretation defines what they experienced very well. In the end they gave a very clear description, although abstract, of an elephant....
Leer más

Moon Machines: The Navigation Computer

In this blog I will discuss the documentary watched in class, titled “Moon Machines: The Navigation Computer” produced by the Science Channel. The documentary is about the computer created for the Apollo missions to the moon. Its not the first time I’ve watched this documentary, but I still find msyelf captivated by the genius of the people behind this project. Nowadays we have computers that are far more powerful (and smaller) than the ones used in Apollo missions. But, for its time, the Apollo computers where state of the art and required a tremendous amount of engineering. The programming done in the computers of the Apollo missions where somewhat “primitive”, since they used cables going through rings to specify if it indicated a “1” or a “0”. Because of this, the programming took a lot of time, and it was really important it didn't have any errors. Nevertheless, they achieved a lot with this method and where successful in every mission. If we compared that type of prog...
Leer más