Software Architecture Patterns - Book Review

So today I'm bringing another tip from a book, this is not really a book but a kind of report the tip is Software Architecture Patterns.

 

 

  

This book is a very small book so I'm not considering exactly a book, but the information is worth a lot. 

 The material brings a general review about some main software architecture models and brings the positives and negatives of each model. Among the models are: 

 

- Layered Architecture 

- Event-Driven Architecture 

- Microkernel Architecture 

- Microservices Architecture 

- Space-Based Architecture 

 

For the first Layered Architecture model, there is a very common model where the application is divided into front-end, logic and database. 

The second Event-Driven Architecture model is presented as one of the main models for applications with high traffic volume and intensive workload. In this architecture there is no central processing point the load can be split between different components that can perform tasks in parallel until, this in an event-driven architecture form there is another way brought in where tasks are executed sequentially, the author until exemplify with a stick race where each component performs its part of the work and moves on to the next component. 

Microkernel Architecture is an architecture model to be considered where a very lean application is developed with minimum requirements and then other components can be "attached" as needed. 

The microservices architecture, which is one of the ones that is standing out a lot in the development of applications, is one of the main ones brought by the author. It consists of breaking a monolithic application into small "microservices" pieces and developing each of these parts independently, using APIs for communication between services. 

Space-Based Architecture is an architecture brought by the author that I didn't really understand, my experience as a developer is small and I'm looking to learn, but it's an architecture that uses some components like cache and even grids. It is worth reading this part of the book and also a research to correctly understand this model. 

 

 

That's it, a reading is always valid. Vlw!

 

Website: https://www.intelligencesoftware.com.br

Ads: https://ads.intelligencesoftware.com.br