Chapter 12 Flashcards
Name 5 Architectural Patterns
Leader-Follower
Two-Tier Client-Server
Multi-Tier Client-Server
Distributed Components and SOA
Peer-to-Peer
Leader-Follower Pattern
Leader is the brain and handles computation. Followers are limbs and handle specific tasks.
When to use Two-Tier Client-Server
Used when the system needs to be more centralized for security reasons.
Two forms of two-tier client-server
Thin Client - More strain on the server side
Fat Client - More strain on the client side
Thin Client Pros and Cons
Pro: Clients easier to manage
Cons: Places a heavy processing load on the server and the network
Reason to use Multi-Tier over TwoTier
More scalability. Different layers can operate on different processors. Can operate with hundreds or thousands of clients.
How to organize Layered Pattern
Design system as a set of services without trying to allocate the services to the layers
How are Distributed Components accessed?
Through middleware that uses remote procedures or method calls.
Benefits of the Distributed Components Pattern
Flexibility, Openness, Scalability, Reconfiguration Easiness.
Example of A Distributed Component Pattern
Data-Mining
Disadvantages of the Distributed Component Pattern
More complex to design than client-server - More costly
No universal standard for distributed components or middleware. Different vendors have incompatible middleware
Reason to use Service-Oriented-Architecture over Distributed Component Pattern
SOA is message-based (asynchronous). Does not rely on middleware, less issues with compatibility.
Reason to use Distributed Component Pattern over Service-Oriented-Architecture
Remote Procedure Calls are faster than messaging so Distributed Component is better for high throughput systems than SOA.
How is Peer-To-Peer (P2P Different than Client-Server
P2P is similar to Client-Server but without the distinctions.
Advantages of P2P
No central server.
Highly redundant
