# MQTT - Another Implementor's Perspective

DevFeed: [MQTT - Another Implementor's Perspective](<https://devfeed.tech/articles/mqtt-another-implementor-s-perspective-33404.md>)

Original publisher: [Read original article](<https://timkellogg.me/blog/2014/06/02/MQTT-another-implementors-perspective>)

Published: 2014-06-02T00:00:00Z

Content type: opinion

Language: en

Sources: [Tim Kellogg](<https://devfeed.tech/sources/tim-kellogg.md>)

Topics: [MQTT](<https://devfeed.tech/topics/mqtt.md>), [Protocol (disambiguation)](<https://devfeed.tech/topics/protocol.md>), [Messaging](<https://devfeed.tech/topics/messaging.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [blog](<https://devfeed.tech/tags/blog.md>), [blog-post](<https://devfeed.tech/tags/blog-post.md>), [client](<https://devfeed.tech/tags/client.md>), [community](<https://devfeed.tech/tags/community.md>), [mqtt](<https://devfeed.tech/tags/mqtt.md>), [standards](<https://devfeed.tech/tags/standards.md>)

## AI overview

An implementor responds to criticisms of MQTT, arguing that the protocol is intended to be lightweight, open, simple, and easy to implement rather than highly extensible. The article discusses MQTT's governance, implementation complexity, and client-focused design.

## Source excerpt

Earlier there was a blog post by Clemens Vasters that flamed MQTT. My preference is to take these complaints to the standards bodies responsible for MQTT and try to make constructive changes, but it appears that this is a man who prefers flame wars over professional dialog. I've been challenged to write a rebuttal, so here it is.