s/w-architecture-luisalcantara

Monolith applications is now a thing from the past. In order to build scalable and efficient applications, a new architectural style has come to try and solve the problems of deploying again and again the entire  code when a single change or modifications has been made to a single part of the project. I found logically correct to segment the application into units called services (each one with a specific purpose) and handle it like an independent application.  Web development and applications are growing, and considering that this will keep trending, HTTP is used as a communication method between services. How it is properly done? Through this incredible and standardized interfaces called APIs (Application Programming Interfaces). Since I learned Javascript,  when defining the routes I was already thinking in the required methods (GET, POST; PUT, DELETE, etc) and the scope for each one of them. Therefore, knowing about HTTP and APis will be (if it is not now) a necessary skill.  I was

We are still in the software crisis, and because of that, we still need to develop new methodoligies and strategies in order to mitigate as much as we can this problem. When programming and software engineering arrived, at the first stages people relied on cascade methods, meaning that the phases of a project were done straight. This time, almost everyday we are seeing new programming languages being created, new libraries, frameworks, cloud tools, and technologies that came to change how we develop and operate applications (for example Docker containers and Kubernetes).  Engineers should need to be prepared for a correct structure of their code, design and project. Corporations and organizations should not try to get better their product or solution by adding new methods or practices, instead, they should rather focus in the responsibles of generating the code, I mean, the programmers or coders.  I like the analogy of programmers being craftsmen. After hearing the podcast I had curios