Last week’s article described the difficulties faced by developers when working with distributed and/or microservice architectures, often lacking in-depth knowledge about the underlying network technologies that enable different components of the architectures to communicate.
Microservice-based architectures are changing the way we design software today, raising new challenges in development and operations. These architectures are adding a strong network dependency on business logic, increasing the number of potential hazards, which grow proportionally to the connections or links that are created between services.
In a society that is ever increasing its use of technology and showing no signs of slowing down, it is becoming more and more pertinent to ensure the best quality products. Companies are being pushed to reach a wider audience by accelerating innovation and constantly improve its customers´choice within their platform. Striving to advance the development process while perfecting the overall quality and security of software is top priority.
I’ve always been fascinated by the way in which different computing concepts get converted into common knowledge and how, depending on who’s speaking about a certain concept, that person will tend to assimilate it according to their own field of knowledge and action. This article is the result of a conversation I had with a colleague who interpreted DevOps as related to operational efficiency and facilitating business objectives – which is a perfectly accurate view when looked at from their perspective.