Arquitectura de Software

This reading was about Microservices and well microservices is a very simple thing, there are many benefits into using microservices, turning complicated systems or applications into simple services that can me modified without disturbing the architecture of whatever you are building, this means in more specific words that there is modularity into the microservices architecture and this means that the services which we build using this architecture are faster as well as easier to develop, understand an implement. In a big scale development microservices allow us to deploy changes to specific parts of any development without the need of re deploying all the development, just deploying the module in which we are working or that we are going to modify and this reduces complexity as well as time spent into fixing or improving things that our services may use, each microservice provides a firm module boundary allowing different services to be written in different programming languages ...

In this reading we learned about the 4+1 view model, this model is basically a mechanism or methodology designed to separate the different aspects of software into different views or parts so that the stakeholders can focus into all the different parts of software and have a better understanding about this and this not only benefits stakeholders, as it is segmented it benefits every person working into the system from developers to management and this is a great example of why it is smart to segment the architecture into distinct views. The most important point here is that we have a use case view which makes modelling far more efficient and in each project we will have different modeling tools that will support the 4+1 approach and basically this will allow us to have templates that will make everything easier from de the development, to the implementation, to the understanding. The views work in this way, the logical view has the information about the system in general and i...