there are four different architectural styles plus the hybrid architecture when it comes to distribute system the basic idea is to organised logical different components and distribute those computers over the various machines.
- layered architecture
- object based architecture
- data centre architecture
- event based architecture
- hybrid architecture.
Layered architecture
Layered architecture separates layers of components from each other, giving it it a much more modular approach. a well-known example for this is the model that incorporates a layered architecture when interacting with each of the components, each interaction is sequential where a layer will contact the adjacent clear and this process continues until the request is being connected to but in certain cases the implementation can be made so that some layers will be skipped which is called cross-layer coordination through crosslay coordination one can obtain better result due to performance increase the layers on the bottom provide a service to the layers on the stop the request flows from top to bottom where as the response is sent from bottom to top the advantage of using this approach is that the calls always follow in predefined path and that each layer can be easily replaced or modified without affecting the entire architecture the following image is the basic idea of layered architecture style.
Object-based architectures
this architecture style is based on loosely coupled arrangement of objects this has no specific architecture like players like in layers this does not have a sequential set of steps that needs to be carried out for a given call each of the components are referred to as a object where each object can interact with other objects through a given connector or interface there are much more direct where all the different components can interact directly with other components through a direct method call
as shown in the above image communication between object happen as a method invocation these are generally called remote procedure called RPC some popular examples are Java RMI web services and rest API calls.
This has the following properties
- this architecture style is less structured
- component equals to object
- connector equals RPC or RMI
Data centred architecture
as the title suggests this architecture is based on a data centre where the primary communications happens viva us Central data respiratory this common repository can be either active or passive this is more likely a producer consumer problem the producer producer items to a common data store and the consumers can request Tata from it this common repository could even be a simple database but the idea is that the communication between the objects happening through this shared storage this is support different components by providing a persistent storage space for those components such as my SQL database all the information related to the nodes in the system are stored in this system storage in event based architecture access data is only sent and received by those components who have already subscribed.
Event based architecture
the entire communication in this kind of a system happens through events when an event is generated it will be sent to the bus system with this everyone else will be notified telling that such an event has accused so if anyone is interested that node can pull the event from the bus and use it sometimes this event could be data or even a URL to resources
this event occasionally carry data and advantage in this architectural style is that components are loosely coupled so it is easy to add remove and modified components in the system.
this architectural style is based on the publisher subscriber architecture between its not there is no direct communication or coordination.
this event architecture supports several communication styles
- publisher subscriber
- broadcast
- point to point
the major advantage of this architecture is that the components are decoupled in space loosely coupled.
