search

EclipseFdn / sparkplug.eclipse.org

The Eclipse Sparkplug Working Group seeks to drive the evolution and broad adoption of the Eclipse Sparkplug protocol and related technologies that enable the creation of open, collaborative, and interoperable Industrial IoT (IIoT) solutions.
https://sparkplug.eclipse.org
Eclipse Public License 2.0
0 stars 10 forks source link

Add video to the resources page of sparkplug #103

Closed hassanjaber98 closed 3 years ago

hassanjaber98 commented 3 years ago

Video link: https://www.youtube.com/watch?v=PPpdOUYolIY Tittle: Sparkplug Essentials 04 - Sparkplug Key Principles Desc: In this video, we introduce you to the eight key principles for MQTT Sparkplug:

  1. Publish / Subscribe Architecture
  2. Report by Exception
  3. Continuous Session Awareness
  4. Death and Birth Certificates
  5. Persistent Connections
  6. Auto Discovery
  7. Standardized Payload Definition
  8. Standardized Topic Namespace

The Key Principles in Detail

  1. Publish / Subscribe Architecture This displaces the old poll-response pattern, which had certain disadvantages. The modern decoupled publish-subscribe approach enables features like instant messaging and one-to-many communication

  2. Report by Exception Also based on a modern publish-subscribe pattern, Report-By-Exception saves a significant amount of bandwidth and computing power compared to the old poll-response pattern. The communication is also faster and more reliable since it uses push communication and does not need to wait for the next pull-response cycle when data or a device state changes.

  3. Continuous Session Awareness This is an important monitoring feature for online/offline states of devices. It provides a correct real-time view of the state of all devices, gateways, and applications in your deployment.

  4. Death and Birth Certificates This feature is used for the management and discovery of device states. As soon as an MQTT client goes online, it is required to send out a birth certificate. When it goes offline, the MQTT broker recognizes the changed state and informs every subscribed client by sending a death certificate.

  5. Persistent Connections All devices, gateways, and applications in a deployment use persistent TCP connections

  6. Auto Discovery Sparkplug provides Plug & Play interoperability. This is ensured by auto-discovery of device states, and what data will get sent.

  7. Standardized Payload Definition Defining a standard data format for all messages guarantees faultless communication between all participants.

  8. Standardized Topic Namespace This is also a requirement for Plug & Play interoperability. A common topic namespace used by all Sparkplug participants.

linkfang commented 3 years ago

Hi @hassanjaber98 , Please preview the changes here: https://deploy-preview-106--eclipsefdn-sparkplug.netlify.app/resources/

hassanjaber98 commented 3 years ago

Thanks looks good!

On Tue., Sep. 7, 2021, 1:34 p.m. Zhou (Link) Fang, @.***> wrote:

Hi @hassanjaber98 https://github.com/hassanjaber98 , Please preview the changes here: https://deploy-preview-106--eclipsefdn-sparkplug.netlify.app/resources/

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/EclipseFdn/sparkplug.eclipse.org/issues/103#issuecomment-914493366, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATHUQN57MMNTKGT4TVUZFRDUAZEJJANCNFSM5DEVGXTA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.