Water Level Monitoring IoT Application †Free Samples to Students

Question: Discuss about the Water Level Monitoring IoT Application. Answer: Introduction: The publish-subscribe paradigm takes the roles of publishers or subscribers of information. The communication model requires that the publishers generate data in the form of reports which are then received and interpreted by the subscribers. In this model, the receivers are not the direct target of the publisher. The receivers get notifications by being ultimately submitted according to the content of the notices. in practice, a subscriber expresses interest by issuing subscriptions for specific notifications from a specific publisher. The result is that the subscriber gets asynchronously alerted for all the notifications remitted by any publisher as long as they match their given subscription(Virgillito, 2003). In the asynchronous state the subscriber does not have to be blocked waiting for notifications to arrive especially in the client-server setup. In this case, the IoT water level monitoring application can continuously receive sensor updates with the request every 1s regardles s of the delay in propagation between the sensor and the application. Implementing the publisher-subscriber communication model saves the architecture a lot of time budget as there are several processes that can run concurrently. From the information above, only the round trip propagation delay will affect the receipt of information as well as the time taken by the sensor to process the data. In modern systems the asynchronous protocols used are the AMQP that utilizes the asynchronous messages. The client code or message sender usually does not wait for a response. On the other hand, the command and response communication model are contained in APDU command is useful in the smart card communication model. The model requires a host component to issue a command to the application component. Signal communicate to acknowledge receipt of the command. The sensor device processes the data and sends it to the application indicating completion of a task. There is a lot of delay especially if the sensor takes long to process the data before sending. It may also encounter a hitch and delay the response even further. Therefore, the publisher-subscriber communication model is preferred as it saves the communication process a great deal of lag. The request-response model, it is expected that the response does not experience a lag hence it is used in real time applications(Microsoft, 26). When used for applications that experience a lag, the system is redesigned to use the publisher-subscriber model. References Microsoft. (26, May 2017). Communication between microservices. Retrieved from Microsoft: https://docs.microsoft.com/en-us/dotnet/standard/microservices-architecture/architect-microservice-container-applications/communication-between-microservices Virgillito, A. (2003). Publish/Subscribe Communication Systems: from Models to Applications. Roma: Universita Degli Studi di Roma.