S/W Design and Arch Nat's Blog

We have this premise for the Ready Player One book, that leaves into this world where a virtual reality it's a refugee for this cruel reality. I find some interesting similarities with our actual world, getting us into this new virtual world having our relations using social networks, getting our food, clothes and almost everything using apps, there is so many things that have been evolving to maybe lead us to a similar future like the Ready Player One. In time we may have something similar, that kind of possibilities are evolving really fast, and the total immersion into virtual world it's a classic science fiction fantasy, if we got to the moon, we can do this, the only question is, how long do we have to wait. Living into a different reality, just because our reality is that broken that no one can think a way for the repair, it definitively sounds like us, so many people trying to avoid problems using the video games, giving appearances via Instagram and having this hole f

The microservices architecture is a recent term used for this new perspective for the software architecture, and it's based on getting several small services running into a single application that are communicating constantly with the computer via API using HTTP. This information may appear a little so technical but will get relevant at the time of understanding it's structure and purpose. It may appear that is not that different for the traditional model of architectures like the libraries but the microservices get you benefits like the independence of the services, every service could be used and saving a lot of processing for each application opened. This independence also helps at the moment of creating efficient interfaces and to get explicitly the function of every service. The changes in organization, and the approach changing from a project model to a product model, are also differentiators that makes interesting changes for the microservices perspecti

For this week we have several material to use, and I found it great. First the video that gets us the theory for the 4 different perspective model architecture plus 1, this part of the homework is connected to video that told us a story about the blind men who touched an elephant, and this two are necessary for fully understand the last article, getting combined into this new story about the programmers that found a new program thing and get to understand it in different ways. Its important to mention first the 4+1 model and each view of it, getting initialy the logical view explaining the behavior of components using state machine or sequence diagrams, the process view that gets the way of communication for the different system processes, also we got the development view that describes the elements and the components for the system in order to be completed, at last for the fourth view we got the physical view giving us the physical distribution for the components as well as the topo

The first interesting topic I find here is focused for the object-oriented programming, but even with that this in mind, we find it useful for other purposes. This might appear a little out of place, but the distinction here is necessary, because I've felt that some concepts are strongly related to the OOP. Anyways, we have here five solid principles for design and getting the code more intuitive and to avoid the most dependencies that we can. The first principle is the "Single responsibility" one and the name is very explicit, it's for getting each class doing one and just one thing, this I see that applies for the methods too, getting in the example some problems for a method that does more than one task. I would ad to this that the name would explicitly say what does each method do, because this is also a problem clearly presented. The second principle is called "Open/Closed principle" and refers to get the classes/functions to be open to the extensio