1-3: "Software Architecture"

It is incredible the importance of the software architecture. Sometimes (certainly most of the times), this step in the software development, we tend to not pay the correct attention to this step and that will lead our development to critical points (in the future).

It is important to take the time you need to accomplish this step in order to develop programs that has the opportunity to scale and become bigger and bigger with the less programming work adapting the classes in order to deliver the new functionality that the client asked.

Also, it is important to know all the different kind of architecture that exists in order of being able to select the right one depending of the software project you are working in. Some of this different software architectures are the following ones:

  1. No architecture: Yes, it is weird to consider this, but it has a reason why to consider it. In this architecture you do not count with no architecture, this is a horrendous mistake because if you do not count with at least one architecture your project will be condemned to fail or to be difficult enough to modify and scale.
  2. Layered Architecture: This architecture is the most used and common in the industry. This architecture describes a system as a hierarchy of layers.
  3. Pipe and Filter Architecture: This architecture models the logical flow of data through a system.
  4. Client/Server Architecture: This architecture separates functionality into two key pieces: The client part and the server part; this architecture, it is also called Two tier architecture.
  5. Component based architecture: This architecture decentralizes control and splits it into a number of separate collaborating components rather than a single monolithic structure.
  6. Framework: Last but not least, we have the framework architecture, this kind of architecture is an extensible library of code that forms a reusable design solution for a particular problem domain.

But it is important to keep in mind that if you want to achieve a good architecture design you need it to be simple. Also, you have to find the equilibrium between having lots of components and having few components. Remember that the architecture design identifies the key components of the system and how they interact, it does not define how they work.

Comentarios

Publicar un comentario

Entradas populares de este blog

Summary Second Period

Imagen
So far we have been seeing a lot of different things this second period. So it is important to make a summary of all that topics that covered this second period. In this occasion the second record exam will cover the following topics: Design Patterns covered in the theory book. Microservices. SOLID principles. The 4+1 view model. As I said earlier, this blog entry will be a summary of all these topics but I encourage you to see all your notes, programming activities and even read again the theory book of Olsen. Design Patterns Design Patterns are typical solutions to commonly occurring problems in software design. These patterns were proposed by the Gang of Four: Erich Gamma, John Vlissides, Ralph Johnson and Richard Helm. Template Method Pattern The Template Method Pattern is a behavioral design pattern that defines a skeleton of an algorithm in the superclass but lets subclasses override specific steps of the algorithm without changing its structure. In this kind o
Leer más

2-3: Microservices

We can define Microservices as an architectural style which approach is to develop a single application as a suite of small services, each of them, running its own processes and communicating via lightweight mechanisms, often Microservices uses an HTTP resource API. We also need to compare a traditional monolithic application in order to compare and to give a better explanation of what is a Microservice. A monolithic application puts all its functionality into a single process and scales by replicating the monolith on multiple servers. But, microservices do not work like this, a microservices architecture puts each element of functionality into a separate service and scales by distributing these services across servers, replicating as needed. Having this context, we can have a better idea of what is a Microservice. Now, it is time to enumerate the important characteristics of a Microservice Architecture, have in mind that it does not exist a silver bullet in development so, no
Leer más

2-4: Understanding the SOLID Principles

The first thing that came to my mind when I read the title of the lecture was, what does SOLID stands for? So, first let me contextualize what is SOLID and then explain the meaning of all the letters in this acronym. As I said before, SOLID is an acronym that stands for five principles of object-oriented programming and design. The objective of these principles is the avoidance of dependencies, because the more things you depend on, the greater the chance something will go definitively wrong; these 5 principles are the following ones: S => Single Responsibility Principle (SRP): States that a class should have exactly one responsibility. This means, that it should have exactly one reason (or one class of reasons) that cause it to be changed; nevertheless, many programmers have the superstition about the systems they maintain things like "Don't touch this module" or the difficult task of selecting that single responsibility. O => Open/Close Principle (OCP): St
Leer más