Software Design and Architecture

Taking the next quotations from the book “Ready player one” Morrow wrote in his autobiography that he’d left GSS because … he felt that the OASIS had evolved into something horrible. “It had become a self-imposed prison for humanity,” he wrote. “A pleasant place for the world to hide from its problems while human civilization slowly collapses, primarily due to neglect.” (p. 120) (Halliday speaking) “I created the OASIS because I never felt at home in the real world. I didn’t know how to connect with people there. I was afraid, for all of my life. Right up until I knew it was ending. That was when I realized, as terrifying and painful as reality can be, it’s also the only place where you can find true happiness. Because reality is real.” (p. 364) I am going to express my opinion about some questions written below. Do you agree whit the two previous quotations? Yes, I agree, in some things, is usual for the persons to feel that they do not match in everything, I am a...

Microservices This week the article to discuss is "Microservices" which was witted by  James Lewis and Martin Fowler. So, first of all, the term Microservice Architecture describes a way of designing software in order that applications have functions, as suites of independently small deployable services. As each one of those is running its own processes but should communicate with the others is usual the usage of an HTTP resource API. An interesting thing about Microservices is that this services are built around business capabilities and are independently deployable by automated deployment machinery. Something mentioned in the article that actually I actually liked is that is a bare minimum of centralized management of the services, so they could be written in different programming languages and use different data storage technologies, allowing more flexibility, of course the fact that you can do this, does not mean that you should but it is possible if ne...

4+1 view model This time I am going to write about two videos and an article. Video 4+1 View into Software Architecture: Usually, the creation of software development is preceded of many UML diagrams, which try to create a model of the system. UML contemplates many views of the design, considering manmy points of view, and providing tools (Different diagrams) that make easy the comprehension of the ideas, you could use interaction diagrams, Behavior diagrams and many others.     The problem is that UML is not a development language, so it could not be clear in all the situations. Different situations may use different ways to express how something functions so, Use cases, Class diagrams, Deployment diagrams, Sequence diagram, State machines are options to describe interactions. The video describes a special view, which could help us to complement the vision of a system, to not focus only in one specific layer, With you, ladies and gentleman, the "4+1 ...

This week the blog will talk about the article "Understanding the SOLID Principles" written by Edward Guiness, this is a brief summary that presents the definition of the SOLID Principles. The general objective of the SOLID principles, and so the author in the article, is to implement best practices in the creation of objects and classes in specific cases depending on the situation that is presented. And with you, the 5 principles *drumroll*: • Single Responsibility Principle • Open/Closed Principle • Liskov Substitution Principle • Interface Segregation Principle • Dependency Inversion Principle The first of this is the Single Responsibility Principle, it says that a class, should have just exactly one responsibility, just one reason or an only class of reason to exist. This responsibility should be implemented to the class, so for this reason a class just has one reason to be modified. Why implement this? Easy, in a big project you will have lots of classes ...