Please enable JavaScript.
Coggle requires JavaScript to display documents.
Distributed Architecture, Broker Architecture - Coggle Diagram
Distributed Architecture
-
At least 3 tiers
-
Middle-end tier - Business logic tier
- Manages business logic and execution
Back-end tier - DB management tier
-
Cons
- Difficulty in testing due to lack of testing tools
- Adding multiple servers in the system makes the server reliability and availability even more critical
- The Broker architectural style
-
Broker Style
-
-
-
Advantages
Server component implementation and location transparency,
Changeability and extensibility,
-
-
-
Broker Architecture
Sub-components include
Skeleton (server-side proxy) – encapsulates lower network details, dispatch requests to local service objects
-
Stub (client-side proxy) – provide “stub” version of remote services, responsible for massaging messages
-
-
Stub (Client-side proxy)
The proxy hides inter-process communication at protocol level, marshals the parameter values, and unmarshals results from the server.
-
The stud is generated at compilation time and deployed at client side to be used as a proxy for client
To the client, a remote object appears like a local one.
-
Broker
It stores all servers’
- registration information, their functionalities and location information
It provides APIs for clients to request, servers to respond, registering or unregistering server components, transferring messages, and locating servers.
It coordinates communications, passing on request and returning replies
-
Network
Connects components using designated protocol standards such as
-
-