Software architectural patterns - A Quick Understanding Guide
•
1 like•1,242 views
This document discusses various software architectural patterns. It begins by defining architectural patterns as general and reusable solutions to common software architecture problems within a given context. It then outlines 10 common patterns: layered, client-server, master-slave, pipe-filter, broker, peer-to-peer, event-bus, model-view-controller, blackboard, and interpreter. For each pattern, it briefly describes the pattern and provides examples of its usage. The document aims to provide a quick understanding of architectural patterns.
Report
Share
Software architectural patterns - A Quick Understanding Guide
- 1. Software Architectural Patterns A QUICK UNDERSTANDING GUIDE Mohammed Fazuluddin
- 2. Topics Overview Types Architectural Patterns Overview Of Architectural Patterns Architectural Patterns Pro’s and Con’s
- 3. Overview An architectural pattern is a general, reusable solution to a commonly occurring problem in software architecture within a given context. Architectural patterns are similar to software design patterns but have a broader scope. The architectural patterns address various issues in software engineering, such as computer hardware performance limitations, high availability and minimization of a business risk. Some architectural patterns have been implemented within software frameworks.
- 4. Types Architectural Patterns Following 10 common architectural patterns . Layered pattern Client-server pattern Master-slave pattern Pipe-filter pattern Broker pattern Peer-to-peer pattern Event-bus pattern Model-view-controller pattern Blackboard pattern Interpreter pattern
- 6. Layered pattern This pattern can be used to structure programs that can be decomposed into groups of subtasks, each of which is at a particular level of abstraction. Each layer provides services to the next higher layer. The most commonly found 4 layers of a general information system are as follows. Presentation layer (also known as UI layer) Application layer (also known as service layer) Business logic layer (also known as domain layer) Data access layer (also known as persistence layer) Usage General desktop applications. E commerce web applications.
- 8. Client-server pattern This pattern consists of two parties; a server and multiple clients. The server component will provide services to multiple client components. Clients request services from the server and the server provides relevant services to those clients. Furthermore, the server continues to listen to client requests. Usage Online applications such as email, document sharing and banking.
- 10. Master-slave pattern This pattern consists of two parties; master and slaves. The master component distributes the work among identical slave components, and computes a final result from the results which the slaves return. Usage In database replication, the master database is regarded as the authoritative source, and the slave databases are synchronized to it. Peripherals connected to a bus in a computer system (master and slave drives).
- 12. Pipe-filter pattern This pattern can be used to structure systems which produce and process a stream of data. Each processing step is enclosed within a filter component. Data to be processed is passed through pipes. These pipes can be used for buffering or for synchronization purposes. Usage Compilers. The consecutive filters perform lexical analysis, parsing, semantic analysis, and code generation. Workflows in bioinformatics.
- 13. Broker pattern
- 14. Broker pattern This pattern is used to structure distributed systems with decoupled components. These components can interact with each other by remote service invocations. A broker component is responsible for the coordination of communication among components. Servers publish their capabilities (services and characteristics) to a broker. Clients request a service from the broker, and the broker then redirects the client to a suitable service from its registry. Usage Message broker software such as Apache ActiveMQ, Apache Kafka, RabbitMQ and JBoss Messaging.
- 16. Peer-to-peer pattern In this pattern, individual components are known as peers. Peers may function both as a client, requesting services from other peers, and as a server, providing services to other peers. A peer may act as a client or as a server or as both, and it can change its role dynamically with time. Usage File-sharing networks such as Gnutella and G2) Multimedia protocols such as P2PTV and PDTP.
- 18. Event-bus pattern This pattern primarily deals with events and has 4 major components; event source, event listener, channel and event bus. Sources publish messages to particular channels on an event bus. Listeners subscribe to particular channels. Listeners are notified of messages that are published to a channel to which they have subscribed before. Usage Android development Notification services
- 20. Model-view-controller pattern This pattern, also known as MVC pattern, divides an interactive application in to 3 parts as, model — contains the core functionality and data view — displays the information to the user (more than one view may be defined) controller — handles the input from the user It decouples components and allows efficient code reuse. Usage Architecture for World Wide Web applications in major programming languages. Web frameworks such as Django and Rails.
- 21. Blackboard pattern This pattern is useful for problems for which no deterministic solution strategies are known. blackboard — a structured global memory containing objects from the solution space knowledge source — specialized modules with their own representation control component — selects, configures and executes modules. Usage Speech recognition Vehicle identification and tracking Protein structure identification Sonar signals interpretation.
- 24. Interpreter pattern This pattern is used for designing a component that interprets programs written in a dedicated language. It mainly specifies how to evaluate lines of programs, known as sentences or expressions written in a particular language. The basic idea is to have a class for each symbol of the language. Usage Database query languages such as SQL. Languages used to describe communication protocols.
- 25. Architectural Patterns Pro’s and Con’s
- 26. THANKS If you feel that it is helpful and worthy to share with others then please like and share the same.