Lakhasly

4:20 ص ‎(قبل 0 دقيقة)‎
أنا

1Q) Under which type of distributed systems do wearable devices belong to?

Answer: Wearable devices belong to the category of distributed systems called Mobile and Ubiquitous Computing Systems. These systems consist of various devices, including smartphones, tablets, smartwatches, and other wearable gadgets, that are connected through wireless networks. These devices are designed for mobility, adaptability, and context-awareness, enabling users to access information and computing resources anytime, anywhere.

2Q) Explain about the following:

a) Resource-centered Architectures

Resource-centered Architectures are distributed system architectures that focus on organizing and managing resources, such as computational power, storage, and network capabilities. In these architectures, resources are made available to clients through well-defined interfaces and protocols. Examples of resource-centered architectures include:

• 
  

  Client-Server Architectures: In this model, a central server provides services to various clients. The server is responsible for managing resources, processing client requests, and returning the results. Clients are responsible for requesting services and consuming the results provided by the server.

  
  


• 
  

  Peer-to-Peer (P2P) Architectures: In P2P architectures, nodes (called peers) in the system act as both clients and servers, sharing their resources with other peers in the network. This architecture enables decentralization, scalability, and fault-tolerance, as there is no single point of failure or control.

  
  

  b) Publish-subscribe architectures (Briefly)

  
  

Publish-subscribe architectures are a type of messaging pattern used in distributed systems, where a group of subscribers express interest in receiving specific types of messages. Publishers, on the other hand, generate messages without knowledge of which subscribers, if any, will receive them. A middleware component, called the message broker or event bus, is responsible for filtering and routing messages from publishers to interested subscribers.

This architecture allows for loose coupling between system components, as publishers and subscribers do not need to be aware of each other's existence. It also promotes scalability and flexibility, as new publishers and subscribers can be added or removed with minimal impact on the overall system. Examples of publish-subscribe architectures include message-oriented middleware, such as Apache Kafka and RabbitMQ, and event-driven architectures.