Microservices

Microservices

In their article called "Microservices", James Lewis and Martin Fowler talk about the new trending and future of the design and architecture of software: The microservices architecture. In a general panorama, instead of having one big monolithic application, one must create several different small applications that coordinate with each other and create the bigger perspective for the entire system.This grants flexibility in the entire structure because changes are less expensive, as instead of rebooting the entire system each time there's a change in the requirements, one can just look into the specific microservice that needs to be changed and do it.   

The biggest challenge to tackle in order to begin the implementation of this structure, however, is to manage the synchronous processes, and therefore, create a reliable controller that administrates and instructs the different modules that conform each of the microservices. However, I think it's pretty doable nowadays, and just a matter of time before this new form of architecture prevails on the others.

Obviously, there are a lot of design patterns and strategies that are developed with the focus on monolithic architecture, and another goal should be to focus on multiple layered design and the proper division of work in order to find out more efficient methods and new patterns apliable to this new architecture. 

Finally, another problem I see is that right now, as the great and vast majority of enterprises and companies have implemented monolithic-architecured software and have been running on them for many years, they won't be very inclined in modifying or changing their whole infrastructure (hardware and software) for another architecture that even when it is proved it is more efficient, is not even needed because the previous one fullfilled its job perfectly. I do think it's gonna take more than that to introduce this new architecture in the industry, and it is up to us, the new generation of IT's, to evolve the industry and invite others to adapt into the new models.

Comments

Post a Comment

Popular posts from this blog

War Games

War Games War Games is a sci-fi movie from 1983 that narrates the story of David Lightman, a teenager that trying to hack into what he thought was a videogame development company accessed instead into a top secret military base computer and initialized a "game" called Global Thermonuclear War, which ran a simulation of a nuclear war between the USSR and the USA, driving everybody mad as they thought the simulation was a real deal, and giving a head start to a potential World War 3. Even though it is considered a classic, I must admit I had never seen the movie, not even heard about it. I watched it without knowing a thing about the plot, and I enjoyed it more than I expected to be honest. However there are a lot of things that I found a little absurd and highly unlikely to occur in real life. The plot itself, for instance. Just to think that a kid by accident has the ability to enter a military base is something I found too fictional to my taste, even when we are talking...
Read more

Software Architecture

The power of good software architecture The importance behind a simple, yet efficient design. In the chapter 14 of his book "Code Craft", author and developer Peter GoodLiffe talks about the importance and influence of good software designing. I found it quite practical (and a little unconventional) how he describes the different styles of architecture in software through comparisons with pasta. I was so hungry yet intrigued while reading through the descriptions of each type and the different applications each have for different situations. I always find it overwhelming how easy it can seem to make a good base to develop software, and yet there are so many sources and lectures on how to get it right, as it is clearly underestimated how challenging it can result to make not only a functional software, but flexible, modular, esthetic, and reliable. And the most difficult thing of all is that there are NO right answers. There are NO instructions or guides on how to b...
Read more

Understanding the SOLID Principles

Understanding the SOLID Principles In a section on the book “Ace the Programming Interview: 160 Questions and Answers for Success”, Edward Guiness talks about a set of practices to have simple and efficient code: The SOLID Principles. The acronym stands for:  Single Responsibility Principle Open/Closed Principle Liskov Substitution Principle Interface Segregation Principle Dependency Inversion Principle The Single Responsibility Principle (SRP) states that each class should have one and exactly one responsibility. Only experience and practice will help you determine what one responsibility envolves, The Open/Closed Principle (OCP) says that each class should be open for extension, but closed for modification. When adding new behavior, we should leave the base class alone and instead create new inheriting classes, and avoid unexpected consequences for the original subclasses. The Liskov Substitution Principle (LSP) says that the less inheritance we h...
Read more