Ir al contenido principal

Microservices

Adaptability is always the answer, depending on the environment is how everything else is going to adapt. In the case of micro services, it is known by a new model for the big monolith replacement, but it is not a replacement, is just another type of architecture that had its benefits because certain features it has, but ensuring that micro services is the only path to follow, causes a problem, this architecture is proper for specific scenarios. In the industry, the massive over use of a new technology is often, for newer creations comes the extended massive usage. At this point other creations or technology can be developed to enter the competition scenario, for now, the old monolithic model is left behind, while micro services models are more used and potential growth is heading that way. As mention before, for some scenarios is viable using micro services, but in not the only alternative, it always depend on what is being worked on. It is true that segmentation and modulation can divide the problem and increase performance. But a created architecture is build for a specific reason and context, entities from other context could not be attended to this architecture, the scope is limited at the creation. Software can be a vast abstract space, but it has its own edges, defined by the container, the hardware; A hardware with a biological structure will be so adaptive that the variation of the code and the services would be so dense and ample, which could provide a vast amount of services. The adaptation could be structured by a preferred environment, which exposes the resident’s needs.

The new technologies bring new opportunities to achieve tasks with better performance and approximations that years before, the infinite possibilities for creating new technologies, new architectures is always present. I wonder how architectures will be in the future, there are infinite possibilities waiting to be discovered.

References:

https://martinfowler.com/articles/microservices.html

Comentarios

Entradas más populares de este blog

Who needs an Architect?

“We have met the enemy, and he is us.” Human beings are symbolic animals, we give an interpretation of our observation, recognizing everything as a symbol, creating concepts in order to give meaning to our existence. At first creating certain laws that rule our reality because each concept and law we created makes sense in our own interpretation, from that we continued creating more and more concepts and laws which are based in our preview interpretation, being the architecture of our whole understanding. Society has become the architect of every brick that constructs reality, and the architect is the one who makes the important decisions in order to continue the construction. With one building which has an established basis, and with the expansion during the course of time, it is difficult or even impossible to make changes into the functionality and shape, it could have slightly modifications but it will never change the structure at its roots, the complexity of this system is

WarGames

How far technology can go? It is an often question everyone ask, including such philosophical questions about we humans and our creations, just like our Frankenstein Monster, our creation could bring chaos to ourselves. We have the power to create and the limit of our creation could be bypass by that same creation. This movie called War Games, bring this topic and it is an actual matter, and now even more because now a days technology had reached tremendous power and capacity that is very impressive, some tasks that we humans cannot do, or maybe as fast, are done by our own creation. Just like the arguments of the Android David in the movies Prometheus and Alien Covenant, David reached a conscious level that defined him to be as he was and committing every action during the movie. It is that self evolution that keeps growing and it hasn’t the same limits as human interpretation has. Another example is this classic movie 2001 A Space Odyssey, from S. Kubrik, HAL 9 000, who has e

Understanding the SOLID Principles

T here exist some principles that make a procedure easier to perform, with this resource, it is viable to create clean products. In programming, exist something called SOLID principles that ensure quality and good performance while developing code, this acronym SOLID are the 5 widely accepted principles: S - S ingle Responsibility Principle A class should have exactly one responsibility. O - O pen/Closed Principle A class or a function should be open for extension but closed for modification. L - L isvok Substitution Principle Keep the relationship between classes and functions. I – I nterface Segregation Principle Avoiding interfaces that overloads classes with responsibilities that this classes don’t actually need. D – D ependency Inversion Principle “ Depend upon abstractions not upon concretions.” By understanding each one of this SOLID Principles, we could manage to create good code, and by good code I mean cleaner code that is maint