The must knows of Architectural patterns (12/10/2020)

When thinking about going into the job market for a computer scientist there is a common theme. This includes big enterprises needing systems or designed to be produced in order to benefit you and their operations. Although before even starting this we need to understand Software architecture. An architectural pattern, in general, is considered to be a reusable solution to a commonly occurring problem. within the Architectural pattern, we tend to see a total of 10 different patterns that make up the basic framework. One of these simple frameworks is a layered pattern. this pattern can be used to structure programs that will be decomposed into groups of sub-categories. with this particular pattern, we see it being used in desktop applications and E-commerce web applications. the second pattern we see is a client-server pattern which is made up of a server and multiple clients. This will allow server components which will allow assisting multiple clients among a broad range of devices.  you will be able to find this pattern most frequently in Emails, documents, sharing, and banking. The third pattern that mostly relates to a big data analyst would be the master-slave pattern. The master-slave pattern is able to distribute the work among identical slave components, which will ultimately compute the final results from the results which then gets fed to the slaves to return. this is mainly used in datasets and databases in replication. the database is usually considered an authoritative source and usually synchronized between the databases of slaves and masters.  In inorder for this to work correctly we need to have them connected to a bus in a computer system in a sense of branches where we see that the master usually has 3 slave nodes. The 4th design pattern we usually see is the Pipe filter pattern. A pipe filter pattern can be used to structure systems that produce and process a stream of data. Each of the said processes is enclosed within the filter component, which allows the data to be processed through pipes. you can think of these pipes to be as a buffer so the data can be synchronized in the dataset if new data arrives. As well you may think of the architectural pattern as a pattern which recurring a solution to a recurring problem. in most cases, you are able to figure out which classes we have as well as how they will interact with each other to see how they will be implemented in a sequence of systems. usually, an Architectural pattern has the most impact in regard to the code which will then impact the whole application usually horizontally or vertically.