From 39b4c2c73f2cfc04a6f795c87434ac24008ae47c Mon Sep 17 00:00:00 2001 From: Swilder-M Date: Thu, 13 Jun 2024 17:00:07 +0800 Subject: [PATCH] chore(en): modify emqx.io links Signed-off-by: Swilder-M --- ...introduction-to-the-commonly-used-mqtt-client-library.md | 2 +- .../application-of-mqtt-protocol-in-oil-and-gas-industry.md | 2 +- en/202107/introducing-emqx-cloud-on-microsoft-azure.md | 2 +- en/202108/how-to-use-mqtt-in-php.md | 2 +- en/202108/mqtt-broker-clustering-part-1-load-balancing.md | 2 +- ...allenges-and-solutions-of-emqx-horizontal-scalability.md | 2 +- en/202111/emqx-newsletter-202110.md | 2 +- en/202111/ios-mqtt5-client.md | 2 +- en/202111/popular-online-public-mqtt-brokers.md | 2 +- en/202112/emqx-newsletter-202111.md | 2 +- .../introduction-to-the-open-source-testing-tool-jmeter.md | 2 +- en/202201/mqtt-for-elixir.md | 2 +- en/202201/mqttx-v-1-7-0-release-notes.md | 2 +- en/202201/mqttx-v-1-7-2-release-notes.md | 2 +- .../advanced-testing-of-erlang-and-elixir-applications.md | 2 +- en/202202/building-emqx-releases-with-elixirs-mix.md | 2 +- en/202202/emq-is-now-the-foundational-member-of-oasis.md | 2 +- ...x-v-4-4-new-feature-a-top-view-of-slowest-subscribers.md | 2 +- .../how-emqx-5-0-achieves-100-million-mqtt-connections.md | 2 +- en/202208/hstreamdb-newsletter-202206.md | 2 +- .../powerful-and-easy-to-use-mqtt-5-command-line-tool.md | 2 +- en/202209/iot-data-integration.md | 2 +- en/202209/mqtt-persistence-based-on-rocksdb.md | 2 +- ...o-set-parameters-when-establishing-an-mqtt-connection.md | 2 +- en/202211/mqtt5-features-retain-message.md | 2 +- en/202212/emqx-prometheus-grafana.md | 2 +- en/202212/mqtt-session.md | 2 +- en/202212/reflections-on-the-tenth-anniversary-of-emqx.md | 2 +- en/202212/we-d-appreciate-your-feedback.md | 2 +- en/202303/7-mqtt-trends-in-2023.md | 2 +- ...curing-mqtt-with-username-and-password-authentication.md | 2 +- en/202304/emqx-vs-mosquitto-2023-mqtt-broker-comparison.md | 4 ++-- en/202304/emqx-vs-nanomq-2023-mqtt-broker-comparison.md | 4 ++-- en/202304/emqx-vs-vernemq-2023-mqtt-broker-comparison.md | 4 ++-- .../mosquitto-vs-nanomq-2023-mqtt-broker-comparison.md | 2 +- .../open-mqtt-benchmarking-comparison-emqx-vs-mosquitto.md | 2 +- ...rotocol-the-features-use-cases-and-impact-for-iot-iov.md | 2 +- en/202305/can-bus-how-it-works-pros-and-cons.md | 4 ++-- en/202305/emqx-mqtt-broker-connection-troubleshooting.md | 2 +- ...er-deployment-troubleshooting-ensuring-a-smooth-start.md | 2 +- ...started-with-rule-engine-in-mqtt-broker-a-quick-guide.md | 4 ++-- en/202305/how-to-use-mqtt-in-nodejs.md | 2 +- en/202305/mqtt-broker-clustering.md | 2 +- en/202305/mqtt-js-tutorial.md | 2 +- ...atural-interactions-in-iot-combining-mqtt-and-chatgpt.md | 6 +++--- ...ick-deploying-emqx-mqtt-broker-on-aws-using-terraform.md | 2 +- ...ick-deploying-emqx-mqtt-broker-on-gcp-using-terraform.md | 2 +- ...3-open-source-mqtt-brokers-for-industrial-iot-in-2023.md | 6 +++--- en/202305/using-terraform-to-deploy-emqx-mqtt-broker.md | 4 ++-- ...into-token-based-authentication-and-oauth-2-0-in-mqtt.md | 2 +- en/202306/advanced-features-of-mqtt-topics.md | 2 +- en/202306/bridging-modbus-data-to-mqtt-for-iiot.md | 6 +++--- ...build-mqtt-dashboard-with-emqx-grafana-and-prometheus.md | 2 +- en/202306/connect-to-mqtt-broker-with-websocket.md | 2 +- .../enabling-mqtt-over-quic-on-kubernetes-with-emqx-5-0.md | 2 +- .../fortifying-mqtt-communication-security-with-ssl-tls.md | 2 +- ...liability-and-security-of-mqtt-broker-with-rate-limit.md | 2 +- .../leveraging-enhanced-authentication-for-mqtt-security.md | 2 +- ...lug-solution-for-industrial-iot-using-emqx-and-neuron.md | 4 ++-- en/202306/mqtt-stream-processing-with-emqx-and-ekuiper.md | 2 +- en/202306/overcoming-address-change-with-mqtt-over-quic.md | 2 +- ...g-3-0-advancements-and-formalization-in-mqtt-for-iiot.md | 2 +- en/202306/use-mqtt-with-raspberry-pi.md | 2 +- en/202306/what-is-the-mqtt-protocol.md | 2 +- en/202307/bridging-twincat-data-to-mqtt.md | 2 +- ...ed-mqtt-message-storage-using-rocksdb-for-emqx-broker.md | 2 +- .../emqx-mqtt-broker-authentication-troubleshooting.md | 2 +- en/202307/time-series-database-for-iot-the-missing-piece.md | 2 +- en/202308/bridging-opc-ua-data-to-mqtt-for-iiot.md | 2 +- ...-mqtt-broker-troubleshooting-publish-subscribe-issues.md | 2 +- en/202308/emqx-single-node-supports-5m-connections.md | 2 +- ...plained-examples-technologies-benefits-and-challenges.md | 2 +- ...ot-in-the-cloud-8-key-benefits-and-how-to-get-started.md | 2 +- ...-future-crafting-iot-scenarios-with-chatgpt-and-mqttx.md | 4 ++-- en/202309/demonstrate-mqtt-5-0-features-using-mqttx-cli.md | 2 +- .../home-assistant-and-mqtt-4-things-you-could-build.md | 2 +- en/202309/mqtt-5-0-control-packets-06-auth.md | 2 +- .../emq-intel-and-sjtu-explore-mqtt-over-quic-together.md | 2 +- en/202310/iiot-vs-iot-examples-and-5-key-differences.md | 2 +- en/202310/industrial-iot-applications.md | 2 +- en/202310/introduction-to-mqtt-5.md | 2 +- ...5-new-feature-clean-start-and-session-expiry-interval.md | 2 +- en/202310/navigating-urban-traffic-with-ekuiper.md | 2 +- en/202310/opc-ua-protocol.md | 2 +- ...he-basics-and-benefits-for-mqtt-and-iot-observability.md | 2 +- ...-a-smart-factory-key-components-4-levels-of-evolution.md | 2 +- en/202311/knx-protocol.md | 2 +- en/202311/running-mqtt-on-kubernetes.md | 2 +- en/202312/coap-protocol.md | 2 +- en/202312/running-mqtt-broker-on-docker.md | 2 +- en/202401/mqtt-with-zigbee-a-practical-guide.md | 2 +- .../mqtt-sparkplug-bridging-it-and-ot-in-industry-4-0.md | 2 +- .../mqtt-sparkplug-in-action-a-step-by-step-tutorial.md | 4 ++-- en/202403/mqtt-and-kafka.md | 2 +- en/202404/emqx-open-source-vs-enterprise.md | 2 +- en/202404/free-mqtt-broker.md | 2 +- ja/202305/how-to-use-mqtt-in-nodejs.md | 4 ++-- ...3-open-source-mqtt-brokers-for-industrial-iot-in-2023.md | 6 +++--- ja/202306/can-bus-how-it-works-pros-and-cons.md | 4 ++-- ja/202306/emqx-vs-mosquitto-2023-mqtt-broker-comparison.md | 4 ++-- ja/202306/esp32-connects-to-the-free-public-mqtt-broker.md | 2 +- ja/202306/how-to-use-mqtt-in-python.md | 4 ++-- ja/202306/mqtt-client-tools.md | 2 +- ja/202306/mqtt-js-tutorial.md | 2 +- ...rotocol-the-features-use-cases-and-impact-for-iot-iov.md | 2 +- ja/202306/the-easiest-guide-to-getting-started-with-mqtt.md | 2 +- ja/202307/connect-to-mqtt-broker-with-websocket.md | 4 ++-- ...lug-solution-for-industrial-iot-using-emqx-and-neuron.md | 4 ++-- ...ick-deploying-emqx-mqtt-broker-on-aws-using-terraform.md | 2 +- ...g-3-0-advancements-and-formalization-in-mqtt-for-iiot.md | 2 +- ja/202307/the-ultimate-guide-to-mqtt-broker-comparison.md | 4 ++-- ja/202308/emqx-single-node-supports-5m-connections.md | 2 +- ...plained-examples-technologies-benefits-and-challenges.md | 2 +- .../mqtt-sparkplug-in-action-a-step-by-step-tutorial.md | 4 ++-- ja/202308/use-mqtt-with-raspberry-pi.md | 2 +- ja/202309/advanced-features-of-mqtt-topics.md | 2 +- ja/202309/demonstrate-mqtt-5-0-features-using-mqttx-cli.md | 2 +- ...o-set-parameters-when-establishing-an-mqtt-connection.md | 2 +- ...-future-crafting-iot-scenarios-with-chatgpt-and-mqttx.md | 4 ++-- ja/202309/the-smart-manufacturing-revolution.md | 2 +- ja/202309/what-is-the-mqtt-protocol.md | 2 +- .../leveraging-enhanced-authentication-for-mqtt-security.md | 2 +- ja/202310/mqtt-session.md | 2 +- ...curing-mqtt-with-username-and-password-authentication.md | 2 +- .../fortifying-mqtt-communication-security-with-ssl-tls.md | 2 +- ...liability-and-security-of-mqtt-broker-with-rate-limit.md | 2 +- ja/202312/how-to-use-mqtt-in-php.md | 2 +- .../subscription-identifier-and-subscription-options.md | 2 +- ja/202403/bridging-opc-ua-data-to-mqtt-for-iiot.md | 2 +- ja/202403/bridging-twincat-data-to-mqtt.md | 2 +- ja/202403/coap-protocol.md | 2 +- ja/202403/knx-protocol.md | 2 +- ja/202403/opc-ua-protocol.md | 2 +- ja/202403/using-mqtt-in-flutter.md | 2 +- ja/202404/bridging-modbus-data-to-mqtt-for-iiot.md | 6 +++--- ja/202404/mqtt-and-kafka.md | 2 +- 136 files changed, 164 insertions(+), 164 deletions(-) diff --git a/en/201911/introduction-to-the-commonly-used-mqtt-client-library.md b/en/201911/introduction-to-the-commonly-used-mqtt-client-library.md index 00c783cc..74fa5823 100644 --- a/en/201911/introduction-to-the-commonly-used-mqtt-client-library.md +++ b/en/201911/introduction-to-the-commonly-used-mqtt-client-library.md @@ -2,7 +2,7 @@ MQTT is a lightweight [publish-subscribe](https://www.emqx.com/en/blog/mqtt-5-introduction-to-publish-subscribe-model) mode messaging protocol designed for IoT applications in low-bandwidth and unstable network environments. MQTT is based on the publish/subscribe paradigm and works on the TCP/IP protocol family. [MQTT protocol](https://www.emqx.com/en/mqtt-guide) is lightweight, simple, open and easy to implement， which makes it suitable for a wide range of applications. -MQTT is based on the client-server communication mode. MQTT server is called as MQTT Broker. Currently, there are many MQTT Brokers in the industry, whose advantages and disadvantages and functional differences will not be discussed in this article. Taking the [most popular MQTT broker - EMQX](https://www.emqx.io/) in the open source community as an example, this article uses the public Broker `broker.emqx.io` provided by [EMQ](https://www.emqx.com/en) , and uses a simple example of connecting Broker, publishing and processing messages by client to summarizes the usage and examples of [MQTT client libraries](https://www.emqx.com/en/mqtt-client-sdk) under different programming languages and platforms. +MQTT is based on the client-server communication mode. MQTT server is called as MQTT Broker. Currently, there are many MQTT Brokers in the industry, whose advantages and disadvantages and functional differences will not be discussed in this article. Taking the [most popular MQTT broker - EMQX](https://github.com/emqx/emqx) in the open source community as an example, this article uses the public Broker `broker.emqx.io` provided by [EMQ](https://www.emqx.com/en) , and uses a simple example of connecting Broker, publishing and processing messages by client to summarizes the usage and examples of [MQTT client libraries](https://www.emqx.com/en/mqtt-client-sdk) under different programming languages and platforms. The selected MQTT client libraries are as follows: diff --git a/en/202107/application-of-mqtt-protocol-in-oil-and-gas-industry.md b/en/202107/application-of-mqtt-protocol-in-oil-and-gas-industry.md index 7596c6b0..416d33f5 100644 --- a/en/202107/application-of-mqtt-protocol-in-oil-and-gas-industry.md +++ b/en/202107/application-of-mqtt-protocol-in-oil-and-gas-industry.md @@ -71,7 +71,7 @@ MQTT protocol has the characteristics of lightweight and high reliable QoS. It c ### Reduce the cost of hardware and software -The lightweight design of MQTT greatly reduces the hardware requirements from the client to the server. In the EMQ cloud-side data collection solution, the highly available [MQTT broker - EMQX](https://www.emqx.io) in the central computer room of the plant and the lightweight edge industrial gateway Neuron used in production and business replace the expensive SCADA system and data collection and storage server on the field-station side, which reduces the overall hardware and software costs by more than 50%. +The lightweight design of MQTT greatly reduces the hardware requirements from the client to the server. In the EMQ cloud-side data collection solution, the highly available [MQTT broker - EMQX](https://github.com/emqx/emqx) in the central computer room of the plant and the lightweight edge industrial gateway Neuron used in production and business replace the expensive SCADA system and data collection and storage server on the field-station side, which reduces the overall hardware and software costs by more than 50%. ### Save labor cost diff --git a/en/202107/introducing-emqx-cloud-on-microsoft-azure.md b/en/202107/introducing-emqx-cloud-on-microsoft-azure.md index ed5c83c0..0efd4605 100644 --- a/en/202107/introducing-emqx-cloud-on-microsoft-azure.md +++ b/en/202107/introducing-emqx-cloud-on-microsoft-azure.md @@ -1,6 +1,6 @@ EMQ, the leader of open-source and cloud-native distributed MQTT broker for IoT, is pleased to announce that EMQX Cloud is now available on Microsoft Azure. -[EMQX Cloud](https://www.emqx.com/en/cloud) is a fully managed MQTT service built on the worldwide used [open-source MQTT broker - EMQX](https://www.emqx.io), which has more than 10 million downloads and hundreds of thousands of deployments around the globe. +[EMQX Cloud](https://www.emqx.com/en/cloud) is a fully managed MQTT service built on the worldwide used [open-source MQTT broker - EMQX](https://github.com/emqx/emqx), which has more than 10 million downloads and hundreds of thousands of deployments around the globe. EMQX Cloud helps our users carry out their IoT projects with [MQTT](https://www.emqx.com/en/mqtt-guide) in a simple way, without the burden of deploying and managing the self-managed MQTT service in multiple regions of the cloud. diff --git a/en/202108/how-to-use-mqtt-in-php.md b/en/202108/how-to-use-mqtt-in-php.md index 570e85d5..a443bc60 100644 --- a/en/202108/how-to-use-mqtt-in-php.md +++ b/en/202108/how-to-use-mqtt-in-php.md @@ -1,6 +1,6 @@ [PHP](https://www.php.net) is a widely-used open source multi-purpose scripting language, which can be embedded in HTML and is especially suitable for Web development. -This article mainly introduces how to use the `php-mqtt/client` client library in PHP projects to implement the functions of connection, subscription, unsubscribing, message receiving and sending between [MQTT client](https://www.emqx.com/en/blog/mqtt-client-tools) and [MQTT broker](https://www.emqx.io). +This article mainly introduces how to use the `php-mqtt/client` client library in PHP projects to implement the functions of connection, subscription, unsubscribing, message receiving and sending between [MQTT client](https://www.emqx.com/en/blog/mqtt-client-tools) and [MQTT broker](https://github.com/emqx/emqx). diff --git a/en/202108/mqtt-broker-clustering-part-1-load-balancing.md b/en/202108/mqtt-broker-clustering-part-1-load-balancing.md index a5386c66..5b11a558 100644 --- a/en/202108/mqtt-broker-clustering-part-1-load-balancing.md +++ b/en/202108/mqtt-broker-clustering-part-1-load-balancing.md @@ -11,7 +11,7 @@ Here is the quote from [https://mqtt.org/](https://mqtt.org/) [MQTT clients](https://www.emqx.com/en/blog/introduction-to-the-commonly-used-mqtt-client-library) are also similar to HTTP clients: they establish TCP connections to a server and send and receive data. The difference is that HTTP uses a request/response model, while MQTT uses a publish/subscribe model. -A real life example: a temperature sensor in the living room periodically publishes its readings to an [MQTT broker](https://www.emqx.io), a smart-home application may subscribe to the temperature readings and make smart-home decisions for you. For example: turn on the AC when it’s above 32 celsius degrees. +A real life example: a temperature sensor in the living room periodically publishes its readings to an MQTT broker, a smart-home application may subscribe to the temperature readings and make smart-home decisions for you. For example: turn on the AC when it’s above 32 celsius degrees. diff --git a/en/202110/mqtt-broker-clustering-part-3-challenges-and-solutions-of-emqx-horizontal-scalability.md b/en/202110/mqtt-broker-clustering-part-3-challenges-and-solutions-of-emqx-horizontal-scalability.md index 5a99d132..9342b582 100644 --- a/en/202110/mqtt-broker-clustering-part-3-challenges-and-solutions-of-emqx-horizontal-scalability.md +++ b/en/202110/mqtt-broker-clustering-part-3-challenges-and-solutions-of-emqx-horizontal-scalability.md @@ -1,6 +1,6 @@ In this blog post, we will introduce some of the improvements of the MQTT broker cluster scalability. We will mostly focus on the database engine that EMQX uses internally and how we improved it in EMQX 5.0. -Before we start, you should know how data is replicated in the EMQX cluster: [EMQX Broker](https://www.emqx.io) stores the runtime information about the topics and clients in [Mnesia](http://erlang.org/doc/man/mnesia.html) database, which helps replicate this data across the cluster. +Before we start, you should know how data is replicated in the EMQX cluster: [EMQX Broker](https://github.com/emqx/emqx) stores the runtime information about the topics and clients in [Mnesia](http://erlang.org/doc/man/mnesia.html) database, which helps replicate this data across the cluster. ## What is Mnesia? diff --git a/en/202111/emqx-newsletter-202110.md b/en/202111/emqx-newsletter-202110.md index 63ed0286..182ca624 100644 --- a/en/202111/emqx-newsletter-202110.md +++ b/en/202111/emqx-newsletter-202110.md @@ -1,4 +1,4 @@ -Besides making EMQX stronger and faster as an [MQTT messaging broker](https://www.emqx.io), we also try hard to make it ops-friendly. From configuration to management API, dashboard UI to live code upgrade, single node docker run to massive scale clustering. +Besides making EMQX stronger and faster as an [MQTT messaging broker](https://www.emqx.com/en/products/emqx), we also try hard to make it ops-friendly. From configuration to management API, dashboard UI to live code upgrade, single node docker run to massive scale clustering. In October, EMQX development teams have been mostly focusing on HTTP management API, the readiness of which will be checkpoint for the beta.2 release. diff --git a/en/202111/ios-mqtt5-client.md b/en/202111/ios-mqtt5-client.md index a7e7de11..fa786e35 100644 --- a/en/202111/ios-mqtt5-client.md +++ b/en/202111/ios-mqtt5-client.md @@ -175,7 +175,7 @@ If you use the APIs related to `beginBackgroundTaskWithName` and `endBackgroundT ## Summary -So far, we have connected the CocoaMQTT client to the public MQTT Broker and realized the connection, message publishing, and subscription between the client and the [MQTT Broker](https://www.emqx.io). +So far, we have connected the CocoaMQTT client to the public MQTT Broker and realized the connection, message publishing, and subscription between the client and the MQTT broker. > Get the code from [https://github.com/emqx/CocoaMQTT/tree/master/Example](https://github.com/emqx/CocoaMQTT/tree/master/Example). diff --git a/en/202111/popular-online-public-mqtt-brokers.md b/en/202111/popular-online-public-mqtt-brokers.md index 6c0907c6..c932abb7 100644 --- a/en/202111/popular-online-public-mqtt-brokers.md +++ b/en/202111/popular-online-public-mqtt-brokers.md @@ -19,7 +19,7 @@ This article selects the following commonly used public MQTT brokers: ### EMQX -It is a free online [MQTT 5 broker](https://www.emqx.io/) provided by [EMQX Cloud](https://www.emqx.com/en/cloud). There are two access points provided, Global and CN, of which EMQX (Global) is deployed in AWS, Oregon, USA, and EMQX (CN) is deployed in Tencent Cloud, Shanghai. +It is a free online [MQTT 5 broker](https://www.emqx.com/en/products/emqx) provided by [EMQX Cloud](https://www.emqx.com/en/cloud). There are two access points provided, Global and CN, of which EMQX (Global) is deployed in AWS, Oregon, USA, and EMQX (CN) is deployed in Tencent Cloud, Shanghai. Both access points are EMQX clusters composed of 2 nodes. Later, more nodes can be automatically added according to the actual access volume and load. According to the background display, the server is based on [EMQX Enterprise](https://www.emqx.com/en/products/emqx) 4.2.6, and the current running time is 128 days. diff --git a/en/202112/emqx-newsletter-202111.md b/en/202112/emqx-newsletter-202111.md index e0145c5d..28c7de80 100644 --- a/en/202112/emqx-newsletter-202111.md +++ b/en/202112/emqx-newsletter-202111.md @@ -88,7 +88,7 @@ The condition of a large number of offline devices may be caused by some externa Forwarding data to non-relational databases is supported by EMQX Cloud. At present, the resource configuration of the rule engine has added support for Alibaba Cloud MongoDB. The rule engine can be used to persist data to MongoDB of Alibaba Cloud. It provides more choices for business developers to achieve data persistence, which makes business landing more easily. -EMQX team is always committed to bringing a better [MQTT broker](https://www.emqx.io) for the IoT era. Please stay tuned on EMQX. +EMQX team is always committed to bringing a better MQTT broker for the IoT era. Please stay tuned on EMQX.
diff --git a/en/202201/introduction-to-the-open-source-testing-tool-jmeter.md b/en/202201/introduction-to-the-open-source-testing-tool-jmeter.md index aeb8d1e4..3598a78b 100644 --- a/en/202201/introduction-to-the-open-source-testing-tool-jmeter.md +++ b/en/202201/introduction-to-the-open-source-testing-tool-jmeter.md @@ -4,7 +4,7 @@ The IoT industry is developing explosively. As the scale of endpoints continues On the one hand, performance test provides a basis for evaluating IoT systems, which can be verified from multiple dimensions of design indicators, scalability and reliability. On the other hand, performance test also helps to optimize IoT systems and find system performance bottlenecks as soon as possible, so as to provide optimization suggestions. In addition, performance test can also assist the formulation of capacity plans and provide a reference for future capacity expansion plan. -The IoT system has the features of large amount of access devices, diverse protocols, complex integration architecture, and frequent cross-departmental development collaboration, which also makes the IoT performance test face many challenges. **This series of articles will take the IoT platform based on [EMQX](https://www.emqx.io) as an example to introduce how to use performance test tools to verify and test platform-related quality indicators.** +The IoT system has the features of large amount of access devices, diverse protocols, complex integration architecture, and frequent cross-departmental development collaboration, which also makes the IoT performance test face many challenges. **This series of articles will take the IoT platform based on [EMQX](https://www.emqx.com/en/products/emqx) as an example to introduce how to use performance test tools to verify and test platform-related quality indicators.** ## Selection of the test tool -- Introduction to JMeter diff --git a/en/202201/mqtt-for-elixir.md b/en/202201/mqtt-for-elixir.md index 402f8e5d..c2edf31f 100644 --- a/en/202201/mqtt-for-elixir.md +++ b/en/202201/mqtt-for-elixir.md @@ -22,7 +22,7 @@ We will demonstrate some of MQTT's advantages in our setup. An essential thing about MQTT is that it simplifies the client's logic, which is critical for embedded devices. This is achieved with the pubsub model: in MQTT, there is no concept of a "server". Instead, all participating entities are clients connecting to a so-called *broker*. Clients *subscribe* to *topics*, *publish* messages to them, and the broker does the routing (and many other things). -A good production-ready broker, like [EMQX](https://www.emqx.io) generally provides not only MQTT routing capabilities but many other interesting features, like +A good production-ready broker, like [EMQX](https://www.emqx.com/en/products/emqx) generally provides not only MQTT routing capabilities but many other interesting features, like - other kinds of connection methods, like WebSockets; - different models of authentication and authorization; diff --git a/en/202201/mqttx-v-1-7-0-release-notes.md b/en/202201/mqttx-v-1-7-0-release-notes.md index ce373e5c..ec6745cd 100644 --- a/en/202201/mqttx-v-1-7-0-release-notes.md +++ b/en/202201/mqttx-v-1-7-0-release-notes.md @@ -19,7 +19,7 @@ In 1.7.0, MQTTX adds a lot of support for the property configuration of MQTT 5.0 To use and test the features of MQTT 5.0, MQTTX v1.7.0 needs to be used with MQTT Broker that supports MQTT 5.0. -Cloud-native distributed [MQTT broker - EMQX](https://www.emqx.io) supports the MQTT 5.0 protocol since version 3.0. It is the first broker in the open-source community to support this protocol specification and is fully compatible with MQTT 3.1 and 3.1.1 protocols. Connecting to EMQX by Using MQTTX, you can quickly use and test the features of MQTT 5.0. +Cloud-native distributed [MQTT broker - EMQX](https://github.com/emqx/emqx) supports the MQTT 5.0 protocol since version 3.0. It is the first broker in the open-source community to support this protocol specification and is fully compatible with MQTT 3.1 and 3.1.1 protocols. Connecting to EMQX by Using MQTTX, you can quickly use and test the features of MQTT 5.0. ### Support MQTT 5.0 User Properties diff --git a/en/202201/mqttx-v-1-7-2-release-notes.md b/en/202201/mqttx-v-1-7-2-release-notes.md index af255e3c..84da510f 100644 --- a/en/202201/mqttx-v-1-7-2-release-notes.md +++ b/en/202201/mqttx-v-1-7-2-release-notes.md @@ -53,6 +53,6 @@ Next, we will focus on the following aspects: ## Conclusion -MQTTX is designed to connect to test MQTT Brokers such as [EMQX](https://www.emqx.io). The one-click connection and a clean graphical interface make it easy to explore and debug MQTT features. MQTTX provides comprehensive testing capabilities for MQTT features. Fully open-source and community-driven makes it integrated with more rich, powerful, user-friendly features. With MQTTX and EMQX - the cloud-native distributed messaging broker, we believe that the test and development of IoT platforms will become easier. +MQTTX is designed to connect to test MQTT Brokers such as [EMQX](https://github.com/emqx/emqx). The one-click connection and a clean graphical interface make it easy to explore and debug MQTT features. MQTTX provides comprehensive testing capabilities for MQTT features. Fully open-source and community-driven makes it integrated with more rich, powerful, user-friendly features. With MQTTX and EMQX - the cloud-native distributed messaging broker, we believe that the test and development of IoT platforms will become easier. The MQTTX project is completely open-source. You can go to [Github](https://github.com/emqx/MQTTX/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc) to submit the problems encountered during use, or fork the MQTTX project to submit a revised PR to us. We will review and deal with it in time. We would also like to thank all users in the community for their contributions and feedback. The use and affirmation of each community user is the driving force for the advancement of our products. diff --git a/en/202202/advanced-testing-of-erlang-and-elixir-applications.md b/en/202202/advanced-testing-of-erlang-and-elixir-applications.md index 13884cd0..771220f9 100644 --- a/en/202202/advanced-testing-of-erlang-and-elixir-applications.md +++ b/en/202202/advanced-testing-of-erlang-and-elixir-applications.md @@ -1,4 +1,4 @@ -One of the defining features of [EMQX](https://www.emqx.io) is its support of clustering: messages in the [MQTT topics](https://www.emqx.com/en/blog/advanced-features-of-mqtt-topics) are forwarded between the broker nodes transparently for the clients. We are developing a system that is fault-tolerant, has high throughput and low latency. Individual nodes can be shut down, restarted or even paused for a long period of time, but the cluster as a whole continues to serve traffic. +One of the defining features of [EMQX](https://www.emqx.com/en/products/emqx) is its support of clustering: messages in the [MQTT topics](https://www.emqx.com/en/blog/advanced-features-of-mqtt-topics) are forwarded between the broker nodes transparently for the clients. We are developing a system that is fault-tolerant, has high throughput and low latency. Individual nodes can be shut down, restarted or even paused for a long period of time, but the cluster as a whole continues to serve traffic. In order to sync and replicate metadata throughout the cluster more efficiently, we've developed Mria: a lightweight eventually-consistent database management system. These features help us create a low-latency, horizontally scalable system, but they also significantly raise the requirements for testing. Development of distributed systems is a notoriously hard problem: some of the most basic assumptions about how the code is executed are not applicable when any part of the system can suddenly die or stutter, when network connections between the nodes may disappear, and the clocks on the different nodes may not be in sync. diff --git a/en/202202/building-emqx-releases-with-elixirs-mix.md b/en/202202/building-emqx-releases-with-elixirs-mix.md index 2c6e066c..f8135767 100644 --- a/en/202202/building-emqx-releases-with-elixirs-mix.md +++ b/en/202202/building-emqx-releases-with-elixirs-mix.md @@ -1,6 +1,6 @@ We are happy to announce that now [EMQX](https://github.com/emqx/emqx/) can be built using Elixir! -What does that mean? EMQX is the most popular open source [MQTT broker](https://www.emqx.io), written in Erlang, which makes it highly scalable and with high-performance real-time message processing. The Erlang EMQX releases will remain as always, and added to that there will be some packages that are built using Elixir's Mix build tool. These work just as the Erlang ones, with the difference that the shell you have available when using EMQX's console is [IEx](https://hexdocs.pm/iex/1.13/IEx.html). +What does that mean? EMQX is the most popular open source MQTT broker, written in Erlang, which makes it highly scalable and with high-performance real-time message processing. The Erlang EMQX releases will remain as always, and added to that there will be some packages that are built using Elixir's Mix build tool. These work just as the Erlang ones, with the difference that the shell you have available when using EMQX's console is [IEx](https://hexdocs.pm/iex/1.13/IEx.html). Here are a few benefits of building with Elixir: diff --git a/en/202202/emq-is-now-the-foundational-member-of-oasis.md b/en/202202/emq-is-now-the-foundational-member-of-oasis.md index 0adc9ef5..dc365ef4 100644 --- a/en/202202/emq-is-now-the-foundational-member-of-oasis.md +++ b/en/202202/emq-is-now-the-foundational-member-of-oasis.md @@ -6,7 +6,7 @@ OASIS Open is one of the most respected, nonprofit international open source and ## Pioneering Participant in MQTT and the IoT Messaging -EMQ has been working on [EMQX](https://www.emqx.io/), the open source distributed MQTT broker which is fully compatible with MQTT 3.1 and 3.1.1 specifications since 2013. Then when MQTT became an OASIS open standard in 2016, we actively engaged in the development and discussion of the MQTT 5.0 specification. It’s EMQX that innovatively introduced the [shared subscription](https://www.emqx.com/en/blog/introduction-to-mqtt5-protocol-shared-subscription) features back when the specification was still in draft form. +EMQ has been working on [EMQX](https://github.com/emqx/emqx), the open source distributed MQTT broker which is fully compatible with MQTT 3.1 and 3.1.1 specifications since 2013. Then when MQTT became an OASIS open standard in 2016, we actively engaged in the development and discussion of the MQTT 5.0 specification. It’s EMQX that innovatively introduced the [shared subscription](https://www.emqx.com/en/blog/introduction-to-mqtt5-protocol-shared-subscription) features back when the specification was still in draft form. One of the most game-changing releases so far came in 2020 when EMQ introduced EMQX 4.0, the world's first cloud-native MQTT 5.0 Server with the full latest specification support. Now EMQX has become the world's most popular cloud-native distributed MQTT broker with a high-performance real-time message processing engine, connecting more than 100 million IoT devices worldwide for IoT data movement, processing and analytics. diff --git a/en/202203/emqx-v-4-4-new-feature-a-top-view-of-slowest-subscribers.md b/en/202203/emqx-v-4-4-new-feature-a-top-view-of-slowest-subscribers.md index c00182ec..5012e425 100644 --- a/en/202203/emqx-v-4-4-new-feature-a-top-view-of-slowest-subscribers.md +++ b/en/202203/emqx-v-4-4-new-feature-a-top-view-of-slowest-subscribers.md @@ -1,6 +1,6 @@ ## Background -As a [MQTT broker](https://www.emqx.io) admin, you may often want to know which clients are the slowest. We have a nice ‘top’ view for you. One option is perhaps to instrument the subscriber code with latency measurements. However given in MQTT world, the subscribers might be devices out in the wild which are hard to upgrade or collect metrics from. +As a MQTT broker admin, you may often want to know which clients are the slowest. We have a nice ‘top’ view for you. One option is perhaps to instrument the subscriber code with latency measurements. However given in MQTT world, the subscribers might be devices out in the wild which are hard to upgrade or collect metrics from. EMQX v4.4 has a nice feature to overcome this challenge. diff --git a/en/202208/how-emqx-5-0-achieves-100-million-mqtt-connections.md b/en/202208/how-emqx-5-0-achieves-100-million-mqtt-connections.md index 026240c5..dc7242c4 100644 --- a/en/202208/how-emqx-5-0-achieves-100-million-mqtt-connections.md +++ b/en/202208/how-emqx-5-0-achieves-100-million-mqtt-connections.md @@ -1,6 +1,6 @@ ## Introduction: Reaching 100M MQTT connections with a single cluster -Not long ago, the scalable distributed IoT [MQTT broker EMQX](https://www.emqx.io/) released version 5.0. This latest milestone version adopts the new back-end storage architecture, Mria database, and refactors the data replication logic. This makes the horizontal scalability of EMQX 5.0 exponentially improved, and it can more reliably carry larger-scale IoT device connections. +Not long ago, the scalable distributed IoT [MQTT broker EMQX](https://github.com/emqx/emqx) released version 5.0. This latest milestone version adopts the new back-end storage architecture, Mria database, and refactors the data replication logic. This makes the horizontal scalability of EMQX 5.0 exponentially improved, and it can more reliably carry larger-scale IoT device connections. In the performance test before the official release of EMQX 5.0, we achieved 100 million MQTT connections + 1 million message throughput per second through a 23-node EMQX cluster for the first time in the world, which also makes EMQX 5.0 the most scalable [MQTT Broker](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison) worldwide so far. diff --git a/en/202208/hstreamdb-newsletter-202206.md b/en/202208/hstreamdb-newsletter-202206.md index 01a05180..50509e93 100644 --- a/en/202208/hstreamdb-newsletter-202206.md +++ b/en/202208/hstreamdb-newsletter-202206.md @@ -26,6 +26,6 @@ The installation instructions can be found at [https://pypi.org/project/hstreamd ## Integration with EMQX -[EMQX](https://www.emqx.io/) is the world's leading open-source MQTT broker developed by EMQ, which is widely used in the field of IoT. This month, in collaboration with the EMQX R&D team, we have completed an efficient integration of EMQX with HStreamDB. The integration will enable users to utilize and achieve one-stop connection, data access, persistent storage and real-time analytics for IoT devices. +[EMQX](https://github.com/emqx/emqx) is the world's leading open-source MQTT broker developed by EMQ, which is widely used in the field of IoT. This month, in collaboration with the EMQX R&D team, we have completed an efficient integration of EMQX with HStreamDB. The integration will enable users to utilize and achieve one-stop connection, data access, persistent storage and real-time analytics for IoT devices. [^1]: Das, A., Gupta, I. and Motivala, A., 2002, June. Swim: Scalable weakly-consistent infection-style process group membership protocol. In *Proceedings International Conference on Dependable Systems and Networks* (pp. 303-312). IEEE. diff --git a/en/202208/powerful-and-easy-to-use-mqtt-5-command-line-tool.md b/en/202208/powerful-and-easy-to-use-mqtt-5-command-line-tool.md index 0b9b325d..ae94510d 100644 --- a/en/202208/powerful-and-easy-to-use-mqtt-5-command-line-tool.md +++ b/en/202208/powerful-and-easy-to-use-mqtt-5-command-line-tool.md @@ -143,7 +143,7 @@ Finally, we test and verify the functionality of the MQTTX CLI by using the MQTT This concludes our testing and verification of the MQTT message publish-subscribe feature using the MQTTX CLI. In addition to the common features mentioned above, the MQTTX CLI also supports setting up last [will messages](https://www.emqx.com/en/blog/use-of-mqtt-will-message), using SSL/TLS to test mqtts connections, and more. MQTT 5.0 connectivity will also be supported in the future. -The release of the MQTTX CLI provides a new option for IoT developers to test MQTT connections. With complete support for command line calls, desktop client downloads, and online browsers, MQTTX 1.8.0 helps users with different use cases to complete the development and debugging of MQTT services or applications, improving their own business capabilities and stability. The easy-to-use test client tool, MQTTX, combined with the efficient, [reliable MQTT broker](https://www.emqx.io/), EMQX, will help IoT developers build competitive IoT platforms and applications. +The release of the MQTTX CLI provides a new option for IoT developers to test MQTT connections. With complete support for command line calls, desktop client downloads, and online browsers, MQTTX 1.8.0 helps users with different use cases to complete the development and debugging of MQTT services or applications, improving their own business capabilities and stability. The easy-to-use test client tool, MQTTX, combined with the efficient, [reliable MQTT broker](https://github.com/emqx/emqx), EMQX, will help IoT developers build competitive IoT platforms and applications. ## Appendix: User Help diff --git a/en/202209/iot-data-integration.md b/en/202209/iot-data-integration.md index 6dd14b38..07d37cc6 100644 --- a/en/202209/iot-data-integration.md +++ b/en/202209/iot-data-integration.md @@ -90,7 +90,7 @@ The following is a comparison of the functional changes from EMQX open-source ve ## Epilogue -In building IoT platforms and applications, it is an essential challenge to process massive amounts of data accurately and in real time according to demand and to interface with upper-level business systems. As an [MQTT-based IoT messaging server](https://www.emqx.io/) that can "connect any device, at any scale, anywhere," EMQX provides powerful, easy-to-use, and constantly improving data integration capabilities to help users tackle these data processing challenges and achieve business innovations. +In building IoT platforms and applications, it is an essential challenge to process massive amounts of data accurately and in real time according to demand and to interface with upper-level business systems. As an [MQTT-based IoT messaging server](https://www.emqx.com/en/products/emqx) that can "connect any device, at any scale, anywhere," EMQX provides powerful, easy-to-use, and constantly improving data integration capabilities to help users tackle these data processing challenges and achieve business innovations.
diff --git a/en/202209/mqtt-persistence-based-on-rocksdb.md b/en/202209/mqtt-persistence-based-on-rocksdb.md index c7f6f323..4398de0a 100644 --- a/en/202209/mqtt-persistence-based-on-rocksdb.md +++ b/en/202209/mqtt-persistence-based-on-rocksdb.md @@ -1,6 +1,6 @@ ## Introduction: Native MQTT session persistence support -The MQTT protocol standard states that the broker must store messages from offline clients. In previous versions, [the open-source version of EMQX ](https://www.emqx.io/)used memory-based session storage, while the enterprise version further provides an external database storage solution for data persistence. +The MQTT protocol standard states that the broker must store messages from offline clients. In previous versions, [the open-source version of EMQX ](https://github.com/emqx/emqx)used memory-based session storage, while the enterprise version further provides an external database storage solution for data persistence. This memory-based, non-persistent session storage is the optimal solution based on a trade-off between throughput and latency, but it still imposes limitations on users in certain scenarios. diff --git a/en/202211/how-to-set-parameters-when-establishing-an-mqtt-connection.md b/en/202211/how-to-set-parameters-when-establishing-an-mqtt-connection.md index 65299278..2f16c66e 100644 --- a/en/202211/how-to-set-parameters-when-establishing-an-mqtt-connection.md +++ b/en/202211/how-to-set-parameters-when-establishing-an-mqtt-connection.md @@ -47,7 +47,7 @@ For example, `mqtt://broker.emqx.io:1883` is a TCP-based MQTT connection address **WebSocket-based connection** -The connection address also needs to contain the Path when using a WebSocket connection. The default Path configured for [EMQX](http://www.emqx.io/) is `/mqtt`. +The connection address also needs to contain the Path when using a WebSocket connection. The default Path configured for [EMQX](https://github.com/emqx/emqx) is `/mqtt`. For example, `ws://broker.emqx.io:8083/mqtt` is a WebSocket-based MQTT connection address, and `wss://broker.emqx.io:8083/mqtt` is a WebSocket-based MQTT secure connection address. diff --git a/en/202211/mqtt5-features-retain-message.md b/en/202211/mqtt5-features-retain-message.md index 32cba5a6..3fbc88e0 100644 --- a/en/202211/mqtt5-features-retain-message.md +++ b/en/202211/mqtt5-features-retain-message.md @@ -84,7 +84,7 @@ Retained messages are not part of session states, meaning retained messages are ## MQTT Retained Messages in EMQX -[EMQX](https://www.emqx.io/) is the most popular MQTT Broker, with over 10 million downloads worldwide. Recently, [EMQX released version 5.0](https://www.emqx.com/en/blog/emqx-v-5-0-released), which achieved [100 million MQTT connections + 1 million message throughput](https://www.emqx.com/en/blog/how-emqx-5-0-achieves-100-million-mqtt-connections) per second through a 23-node cluster, making EMQX 5.0 the most scalable MQTT Broker worldwide so far. +[EMQX](https://github.com/emqx/emqx) is the most popular MQTT Broker, with over 10 million downloads worldwide. Recently, [EMQX released version 5.0](https://www.emqx.com/en/blog/emqx-v-5-0-released), which achieved [100 million MQTT connections + 1 million message throughput](https://www.emqx.com/en/blog/how-emqx-5-0-achieves-100-million-mqtt-connections) per second through a 23-node cluster, making EMQX 5.0 the most scalable MQTT Broker worldwide so far. EMQX 5.0 supports viewing and setting retained messages in the built-in Dashboard. You may use the following command to install EMQX 5.0 open-source version for trial. diff --git a/en/202212/emqx-prometheus-grafana.md b/en/202212/emqx-prometheus-grafana.md index ad7b732b..02e71995 100644 --- a/en/202212/emqx-prometheus-grafana.md +++ b/en/202212/emqx-prometheus-grafana.md @@ -1,4 +1,4 @@ -[EMQX](https://www.emqx.io/) is the most scalable and popular open-source MQTT broker with a high performance that connects 100M+ IoT devices in 1 cluster at 1ms latency. It can move and process millions of MQTT messages per second. The EMQX 5.0 has been verified in test scenarios to scale to 100 million concurrent device connections and is the first product to introduce QUIC to MQTT. +[EMQX](https://github.com/emqx/emqx) is the most scalable and popular open-source MQTT broker with a high performance that connects 100M+ IoT devices in 1 cluster at 1ms latency. It can move and process millions of MQTT messages per second. The EMQX 5.0 has been verified in test scenarios to scale to 100 million concurrent device connections and is the first product to introduce QUIC to MQTT. > EMQX GitHub: [https://github.com/emqx/emqx](https://github.com/emqx/emqx) diff --git a/en/202212/mqtt-session.md b/en/202212/mqtt-session.md index 2579174e..4ae036ad 100644 --- a/en/202212/mqtt-session.md +++ b/en/202212/mqtt-session.md @@ -31,7 +31,7 @@ Clean Session is a flag bit used to control the life cycle of the session state. > **Note:** A Persistent Session can be resumed only if the client connects again using a fixed Client ID. If the Client ID is dynamic, a new Persistent Session will be created after a successful connection. -The following is the Dashboard of the [open-source MQTT broker EMQX](https://www.emqx.io/). You can see that the connection in the diagram is disconnected, but because it is a Persistent Session, it can still be viewed in the Dashboard. +The following is the Dashboard of the [open-source MQTT broker EMQX](https://github.com/emqx/emqx). You can see that the connection in the diagram is disconnected, but because it is a Persistent Session, it can still be viewed in the Dashboard. ![MQTT Connections](https://assets.emqx.com/images/f66ac8daa11ef2ff5df6b466cd81b510.png) diff --git a/en/202212/reflections-on-the-tenth-anniversary-of-emqx.md b/en/202212/reflections-on-the-tenth-anniversary-of-emqx.md index d52bd187..2b4d25d5 100644 --- a/en/202212/reflections-on-the-tenth-anniversary-of-emqx.md +++ b/en/202212/reflections-on-the-tenth-anniversary-of-emqx.md @@ -1,4 +1,4 @@ -This year marks a significant milestone for EMQ. Ten years back, on December 17, 2012, [EMQX](https://www.emqx.io/) was released as an open-source project on GitHub with [this first commit](https://github.com/emqx/emqx/commit/11db16725e76c3072f7b50cd62abc4a0aa6a43ba). +This year marks a significant milestone for EMQ. Ten years back, on December 17, 2012, [EMQX](https://github.com/emqx/emqx) was released as an open-source project on GitHub with [this first commit](https://github.com/emqx/emqx/commit/11db16725e76c3072f7b50cd62abc4a0aa6a43ba). ![First EMQX Commit to GitHub](https://assets.emqx.com/images/9745b032b378bdb1171e342667dc537e.png) diff --git a/en/202212/we-d-appreciate-your-feedback.md b/en/202212/we-d-appreciate-your-feedback.md index 5ccbfba7..1cc01ff4 100644 --- a/en/202212/we-d-appreciate-your-feedback.md +++ b/en/202212/we-d-appreciate-your-feedback.md @@ -1,4 +1,4 @@ -Throughout the year, [EMQX](https://www.emqx.io/) has seen a consistent rise in [GitHub](https://github.com/emqx/emqx) stars and global users. Our outstanding product performance and extensive integration capabilities have also resulted in more and more enterprise users, including GM, SAIC Volkswagen, Ericsson, HPE, Inovonics, and Verifone, as well as partners, like AWS, VMware, Oracle, SAP, and Erlang Solutions, choosing EMQX as part of their component ecosystem for mission-critical IoT applications. +Throughout the year, [EMQX](https://github.com/emqx/emqx) has seen a consistent rise in [GitHub](https://github.com/emqx/emqx) stars and global users. Our outstanding product performance and extensive integration capabilities have also resulted in more and more enterprise users, including GM, SAIC Volkswagen, Ericsson, HPE, Inovonics, and Verifone, as well as partners, like AWS, VMware, Oracle, SAP, and Erlang Solutions, choosing EMQX as part of their component ecosystem for mission-critical IoT applications. We are truly thankful and honored to be your choice and extend our gratitude to all of our open-source contributors. We value your opinions and strive to incorporate your valuable suggestions and ideas at each stage of software development. diff --git a/en/202303/7-mqtt-trends-in-2023.md b/en/202303/7-mqtt-trends-in-2023.md index a5a891d3..ba09473c 100644 --- a/en/202303/7-mqtt-trends-in-2023.md +++ b/en/202303/7-mqtt-trends-in-2023.md @@ -104,7 +104,7 @@ In traditional IIoT systems, OT and IT systems have generally been separate and ![MQTT Unified Namespace](https://assets.emqx.com/images/4bd773c5f0197e690c0c819f75940d95.png) -In 2023, with [EMQX](https://www.emqx.io/) or [NanoMQ](https://nanomq.io/) MQTT broker empowered by [Neuron](https://neugates.io/) Gateway, the latest open source IIoT connectivity server, building a UNS architecture empowered by the most advanced technology from the IT world is just within grasp. +In 2023, with [EMQX](https://github.com/emqx/emqx) or [NanoMQ](https://nanomq.io/) MQTT broker empowered by [Neuron](https://neugates.io/) Gateway, the latest open source IIoT connectivity server, building a UNS architecture empowered by the most advanced technology from the IT world is just within grasp. >Learn more: [Unified Namespace (UNS): Next-Generation Data Fabric for IIoT](https://www.emqx.com/en/blog/unified-namespace-next-generation-data-fabric-for-iiot) diff --git a/en/202303/securing-mqtt-with-username-and-password-authentication.md b/en/202303/securing-mqtt-with-username-and-password-authentication.md index 7d95991a..70d0528c 100644 --- a/en/202303/securing-mqtt-with-username-and-password-authentication.md +++ b/en/202303/securing-mqtt-with-username-and-password-authentication.md @@ -72,7 +72,7 @@ Here are some key takeaways from what we’ve mentioned in this blog, which can ## Summary -In conclusion, password-based authentication plays a critical role in securing [MQTT connections](https://www.emqx.com/en/blog/how-to-set-parameters-when-establishing-an-mqtt-connection) and protecting the integrity of IoT systems. By following best practices for password selection, storage, and transmission, and being aware of common issues like brute-force attacks, IoT developers can help ensure the security of their MQTT networks. As a widely-used MQTT broker with high scalability and availability, [EMQX](https://www.emqx.io/) also offers a range of security measures, including [password-based authentication](https://docs.emqx.com/en/emqx/v5.0/access-control/authn/authn.html), to guarantee the security of users' IoT systems. +In conclusion, password-based authentication plays a critical role in securing [MQTT connections](https://www.emqx.com/en/blog/how-to-set-parameters-when-establishing-an-mqtt-connection) and protecting the integrity of IoT systems. By following best practices for password selection, storage, and transmission, and being aware of common issues like brute-force attacks, IoT developers can help ensure the security of their MQTT networks. As a widely-used MQTT broker with high scalability and availability, [EMQX](https://github.com/emqx/emqx) also offers a range of security measures, including [password-based authentication](https://docs.emqx.com/en/emqx/v5.0/access-control/authn/authn.html), to guarantee the security of users' IoT systems. However, it's important to note that password-based authentication is just one of many authentication methods available in MQTT, and may not always be the best fit for every use case. For instance, more advanced methods like digital certificates or OAuth 2.0 may provide stronger security in certain scenarios. Therefore, it's important for IoT developers to stay up-to-date with the latest authentication methods and choose the one that best meets the needs of their particular application. diff --git a/en/202304/emqx-vs-mosquitto-2023-mqtt-broker-comparison.md b/en/202304/emqx-vs-mosquitto-2023-mqtt-broker-comparison.md index b085f4f9..6fd4a075 100644 --- a/en/202304/emqx-vs-mosquitto-2023-mqtt-broker-comparison.md +++ b/en/202304/emqx-vs-mosquitto-2023-mqtt-broker-comparison.md @@ -2,7 +2,7 @@ MQTT (Message Queuing Telemetry Transport) is a de facto standard messaging protocol for the Internet of Things (IoT). With the growth of IoT, [MQTT brokers](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison) are becoming vital in connecting IoT devices and moving data between connected devices and cloud services. -[EMQX](https://www.emqx.io/) and [Mosquitto](https://www.emqx.com/en/blog/mosquitto-mqtt-broker-pros-cons-tutorial-and-modern-alternatives) are two of the most popular open-source MQTT brokers. EMQX is a highly scalable, distributed MQTT broker with clustering support. Mosquitto is a lightweight MQTT broker with a small footprint and a single-threaded architecture. +[EMQX](https://github.com/emqx/emqx) and [Mosquitto](https://www.emqx.com/en/blog/mosquitto-mqtt-broker-pros-cons-tutorial-and-modern-alternatives) are two of the most popular open-source MQTT brokers. EMQX is a highly scalable, distributed MQTT broker with clustering support. Mosquitto is a lightweight MQTT broker with a small footprint and a single-threaded architecture. This blog post will provide an in-depth comparison of the two brokers in 2023. @@ -249,7 +249,7 @@ In short, you can choose Mosquitto for embedded hardware and IoT edge deployment - [Eclipse Mosquitto](https://mosquitto.org/) - [Eclipse Mosquitto Documentation](https://mosquitto.org/documentation/) -- [EMQX: The World's #1 Open Source Distributed MQTT Broker](https://www.emqx.io/) +- [EMQX: The World's #1 Open Source Distributed MQTT Broker](https://github.com/emqx/emqx) - [EMQX 5.0 Documentation](https://docs.emqx.com/en/emqx/v5.0/) - [EMQX Enterprise Documentation](https://docs.emqx.com/en/enterprise/v5.0/) - [EMQX Operator Documentation](https://docs.emqx.com/en/emqx-operator/latest/) diff --git a/en/202304/emqx-vs-nanomq-2023-mqtt-broker-comparison.md b/en/202304/emqx-vs-nanomq-2023-mqtt-broker-comparison.md index d1183a05..4dd83e95 100644 --- a/en/202304/emqx-vs-nanomq-2023-mqtt-broker-comparison.md +++ b/en/202304/emqx-vs-nanomq-2023-mqtt-broker-comparison.md @@ -1,6 +1,6 @@ ## Introduction -[EMQX](https://www.emqx.io/) and [NanoMQ](https://nanomq.io/) are both [open-source MQTT Brokers](https://www.emqx.com/en/blog/a-comprehensive-comparison-of-open-source-mqtt-brokers-in-2023), initially developed by [EMQ Technologies Inc](https://www.emqx.com/en/about), a leading open-source IoT data infrastructure software provider. +[EMQX](https://github.com/emqx/emqx) and [NanoMQ](https://nanomq.io/) are both [open-source MQTT Brokers](https://www.emqx.com/en/blog/a-comprehensive-comparison-of-open-source-mqtt-brokers-in-2023), initially developed by [EMQ Technologies Inc](https://www.emqx.com/en/about), a leading open-source IoT data infrastructure software provider. EMQX is a highly scalable, distributed MQTT Broker for connecting millions of IoT devices to the cloud, while NanoMQ is a fast and lightweight broker designed for IoT edge. @@ -203,7 +203,7 @@ In short, you can choose to use one or both, catering to different needs and use ## References -1. [EMQX: The World's #1 Open Source Distributed MQTT Broker](https://www.emqx.io/) +1. [EMQX: The World's #1 Open Source Distributed MQTT Broker](https://github.com/emqx/emqx) 2. [NanoMQ: An Ultra-lightweight MQTT Broker for IoT Edge](https://nanomq.io/) 3. [EMQX 5.0 Documentation](https://docs.emqx.com/en/emqx/v5.0/) 4. [NanoMQ Documentation](https://nanomq.io/docs/en/latest/) diff --git a/en/202304/emqx-vs-vernemq-2023-mqtt-broker-comparison.md b/en/202304/emqx-vs-vernemq-2023-mqtt-broker-comparison.md index 083087ed..ae7091fc 100644 --- a/en/202304/emqx-vs-vernemq-2023-mqtt-broker-comparison.md +++ b/en/202304/emqx-vs-vernemq-2023-mqtt-broker-comparison.md @@ -1,6 +1,6 @@ ## Introduction -[EMQX](https://www.emqx.io/) and [VerneMQ](https://vernemq.com/) are open-source, highly scalable distributed MQTT brokers written in Erlang/OTP, known for their robustness, fault tolerance, and scalability. +[EMQX](https://github.com/emqx/emqx) and [VerneMQ](https://vernemq.com/) are open-source, highly scalable distributed MQTT brokers written in Erlang/OTP, known for their robustness, fault tolerance, and scalability. EMQX is now one of the most popular MQTT brokers in the world. While VerneMQ has not been actively developing and maintaining these years. @@ -204,7 +204,7 @@ In short, EMQX is one of the best choices for deploying MQTT brokers in producti - [VerneMQ - A MQTT broker that is scalable, enterprise ready, and open source](https://vernemq.com/) - [VerneMQ Documentation](https://docs.vernemq.com/) -- [EMQX: The World's #1 Open Source Distributed MQTT Broker](https://www.emqx.io/) +- [EMQX: The World's #1 Open Source Distributed MQTT Broker](https://github.com/emqx/emqx) - [EMQX 5.0 Documentation](https://docs.emqx.com/en/emqx/v5.0/) diff --git a/en/202304/mosquitto-vs-nanomq-2023-mqtt-broker-comparison.md b/en/202304/mosquitto-vs-nanomq-2023-mqtt-broker-comparison.md index f239ced2..bc5d5ecb 100644 --- a/en/202304/mosquitto-vs-nanomq-2023-mqtt-broker-comparison.md +++ b/en/202304/mosquitto-vs-nanomq-2023-mqtt-broker-comparison.md @@ -138,7 +138,7 @@ In contrast, NanoMQ may pose a challenge for beginners due to its more advanced ## Bridging to EMQX Cloud -[EMQX Cloud](https://www.emqx.com/en/cloud) is a highly scalable MQTT messaging service built on the open-source distributed [EMQX broker](https://www.emqx.io/). We can easily bridge Mosquitto or NanoMQ at the IoT edge to the EMQX Cloud service. +[EMQX Cloud](https://www.emqx.com/en/cloud) is a highly scalable MQTT messaging service built on the open-source distributed [EMQX broker](https://github.com/emqx/emqx). We can easily bridge Mosquitto or NanoMQ at the IoT edge to the EMQX Cloud service. ![Bridge Mosquitto to EMQX Cloud](https://assets.emqx.com/images/05b6602329f65d45aa2c87d115e2f51e.png) diff --git a/en/202304/open-mqtt-benchmarking-comparison-emqx-vs-mosquitto.md b/en/202304/open-mqtt-benchmarking-comparison-emqx-vs-mosquitto.md index dddd3c49..1b965067 100644 --- a/en/202304/open-mqtt-benchmarking-comparison-emqx-vs-mosquitto.md +++ b/en/202304/open-mqtt-benchmarking-comparison-emqx-vs-mosquitto.md @@ -2,7 +2,7 @@ > > This blog series presents the benchmark test results and aims to help you choose a suitable MQTT broker based on your needs and use cases. -This blog post will provide the benchmarking results of [EMQX](https://www.emqx.io/) and [Mosquitto](https://www.emqx.com/en/blog/mosquitto-mqtt-broker-pros-cons-tutorial-and-modern-alternatives). Additionally, we compare the features and capabilities of both brokers in detail in another post: [Mosquitto vs EMQX | 2023 MQTT Broker Comparison](https://www.emqx.com/en/blog/emqx-vs-mosquitto-2023-mqtt-broker-comparison). +This blog post will provide the benchmarking results of [EMQX](https://github.com/emqx/emqx) and [Mosquitto](https://www.emqx.com/en/blog/mosquitto-mqtt-broker-pros-cons-tutorial-and-modern-alternatives). Additionally, we compare the features and capabilities of both brokers in detail in another post: [Mosquitto vs EMQX | 2023 MQTT Broker Comparison](https://www.emqx.com/en/blog/emqx-vs-mosquitto-2023-mqtt-broker-comparison). ## MQTT Benchmark Scenarios and Use Cases diff --git a/en/202304/quic-protocol-the-features-use-cases-and-impact-for-iot-iov.md b/en/202304/quic-protocol-the-features-use-cases-and-impact-for-iot-iov.md index a08f2f78..bf1fb77b 100644 --- a/en/202304/quic-protocol-the-features-use-cases-and-impact-for-iot-iov.md +++ b/en/202304/quic-protocol-the-features-use-cases-and-impact-for-iot-iov.md @@ -118,7 +118,7 @@ Some use cases for MQTT over QUIC in the Internet of Vehicles include: ## EMQX: The First MQTT Broker to Implement MQTT Over QUIC -[EMQX](https://www.emqx.io/) is a world leading [open-source MQTT broker](https://www.emqx.com/en/blog/a-comprehensive-comparison-of-open-source-mqtt-brokers-in-2023) with a high-performance real-time message processing engine, powering event streaming for IoT devices at massive scale. Starting from version 5.0, EMQX became the first MQTT broker to support MQTT over QUIC, providing a more efficient and secure way of transmitting MQTT messages over modern complex networks, and improving MQTT's performance in certain scenarios. +[EMQX](https://github.com/emqx/emqx) is a world leading [open-source MQTT broker](https://www.emqx.com/en/blog/a-comprehensive-comparison-of-open-source-mqtt-brokers-in-2023) with a high-performance real-time message processing engine, powering event streaming for IoT devices at massive scale. Starting from version 5.0, EMQX became the first MQTT broker to support MQTT over QUIC, providing a more efficient and secure way of transmitting MQTT messages over modern complex networks, and improving MQTT's performance in certain scenarios. The current implementation of EMQX support replaces the transport layer with a QUIC stream where the client initiates the connection and creates a bidirectional stream. EMQX supports two operating modes: diff --git a/en/202305/can-bus-how-it-works-pros-and-cons.md b/en/202305/can-bus-how-it-works-pros-and-cons.md index 350ab325..b981e991 100644 --- a/en/202305/can-bus-how-it-works-pros-and-cons.md +++ b/en/202305/can-bus-how-it-works-pros-and-cons.md @@ -6,7 +6,7 @@ CAN bus was originally designed for automotive applications by Bosch in the 1980 CAN bus data can provide valuable insights into the performance and status of the connected devices. However, collecting and processing CAN bus data can be challenging due to the high data rate, low bandwidth, and variable network conditions. -One possible solution to overcome these challenges is to use [MQTT](https://www.emqx.com/en/mqtt-guide), enabling timely data transmission from cars to cloud even with weak network conditions. [EMQX is an open-source MQTT broker](https://www.emqx.io/) that can help you build a reliable and scalable MQTT infrastructure for collecting CAN bus data. +One possible solution to overcome these challenges is to use [MQTT](https://www.emqx.com/en/mqtt-guide), enabling timely data transmission from cars to cloud even with weak network conditions. [EMQX is an open-source MQTT broker](https://github.com/emqx/emqx) that can help you build a reliable and scalable MQTT infrastructure for collecting CAN bus data. ![Collecting CAN bus data](https://assets.emqx.com/images/e8c8c72601898e841855a8efa306d63e.png) @@ -188,7 +188,7 @@ The most mature usage is to achieve flexible data collection. Besides that, eKui ## Using MQTT to Collect CAN Bus Data -Using an MQTT broker like [EMQX](https://www.emqx.io/) for collecting CAN bus data can offer several benefits, such as: +Using an MQTT broker like [EMQX](https://github.com/emqx/emqx) for collecting CAN bus data can offer several benefits, such as: - Reduced network overhead: MQTT uses a binary format and a minimal header to encode messages, which reduces the network bandwidth consumption and improves the data transmission efficiency. - Increased scalability: MQTT can support thousands of concurrent connections and millions of messages per second with a single broker. This can enable large-scale data collection from multiple CAN bus devices without compromising performance or reliability. diff --git a/en/202305/emqx-mqtt-broker-connection-troubleshooting.md b/en/202305/emqx-mqtt-broker-connection-troubleshooting.md index 803574b2..9114fa69 100644 --- a/en/202305/emqx-mqtt-broker-connection-troubleshooting.md +++ b/en/202305/emqx-mqtt-broker-connection-troubleshooting.md @@ -1,4 +1,4 @@ -> [EMQX](https://www.emqx.io/) is a popular [MQTT Broker](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison) widely used in the Internet of Things(IoT), Industrial IoT ([IIoT](https://www.emqx.com/en/blog/iiot-explained-examples-technologies-benefits-and-challenges)) and Connected Cars. It can connect millions of devices at scale, move and process your IoT data in real-time anywhere with high performance, scalability and reliability. +> [EMQX](https://github.com/emqx/emqx) is a popular [MQTT Broker](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison) widely used in the Internet of Things(IoT), Industrial IoT ([IIoT](https://www.emqx.com/en/blog/iiot-explained-examples-technologies-benefits-and-challenges)) and Connected Cars. It can connect millions of devices at scale, move and process your IoT data in real-time anywhere with high performance, scalability and reliability. > > In this blog series, we will explore common troubleshooting scenarios when using EMQX and provide practical tips and solutions to overcome them. Readers can optimize your MQTT deployment and ensure smooth communication between your devices following this troubleshooting instruction. diff --git a/en/202305/emqx-mqtt-broker-deployment-troubleshooting-ensuring-a-smooth-start.md b/en/202305/emqx-mqtt-broker-deployment-troubleshooting-ensuring-a-smooth-start.md index 2ddf43b1..3827a6da 100644 --- a/en/202305/emqx-mqtt-broker-deployment-troubleshooting-ensuring-a-smooth-start.md +++ b/en/202305/emqx-mqtt-broker-deployment-troubleshooting-ensuring-a-smooth-start.md @@ -1,4 +1,4 @@ -> [EMQX](https://www.emqx.io/) is a popular [MQTT Broker](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison) widely used in the Internet of Things(IoT), Industrial IoT ([IIoT](https://www.emqx.com/en/blog/iiot-explained-examples-technologies-benefits-and-challenges)) and Connected Cars. It can connect millions of devices at scale, move and process your IoT data in real-time anywhere with high performance, scalability and reliability. +> [EMQX](https://github.com/emqx/emqx) is a popular [MQTT Broker](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison) widely used in the Internet of Things(IoT), Industrial IoT ([IIoT](https://www.emqx.com/en/blog/iiot-explained-examples-technologies-benefits-and-challenges)) and Connected Cars. It can connect millions of devices at scale, move and process your IoT data in real-time anywhere with high performance, scalability and reliability. > > In this blog series, we will explore common troubleshooting scenarios when using EMQX and provide practical tips and solutions to overcome them. Readers can optimize your MQTT deployment and ensure smooth communication between your devices following this troubleshooting instruction. diff --git a/en/202305/getting-started-with-rule-engine-in-mqtt-broker-a-quick-guide.md b/en/202305/getting-started-with-rule-engine-in-mqtt-broker-a-quick-guide.md index 108269d6..53c40131 100644 --- a/en/202305/getting-started-with-rule-engine-in-mqtt-broker-a-quick-guide.md +++ b/en/202305/getting-started-with-rule-engine-in-mqtt-broker-a-quick-guide.md @@ -1,6 +1,6 @@ ## Introduction -A rule engine is a software system that utilizes predefined rules to make decisions or take actions based on input data. In this blog post, we will introduce the Rule Engine in [EMQX MQTT Broker](https://www.emqx.io/) and explains why it is essential for MQTT message transformation and data integration. We will also provide a quick guide with examples to help you get started with Rule Engine for MQTT. +A rule engine is a software system that utilizes predefined rules to make decisions or take actions based on input data. In this blog post, we will introduce the Rule Engine in [EMQX MQTT Broker](https://github.com/emqx/emqx) and explains why it is essential for MQTT message transformation and data integration. We will also provide a quick guide with examples to help you get started with Rule Engine for MQTT. ## What is Rule Engine for MQTT? @@ -18,7 +18,7 @@ The rule engine has a wide range of applications in [MQTT brokers](https://www.e ## EMQX’s Built-in, Out-of-Box Rule Engine -[EMQX](https://www.emqx.io/) is an open-source, highly scalable MQTT broker integrated with an embedded rule engine component. It allows users to quickly implement business logic on data processing with low code, simplifying their software architecture's complexity. +[EMQX](https://github.com/emqx/emqx) is an open-source, highly scalable MQTT broker integrated with an embedded rule engine component. It allows users to quickly implement business logic on data processing with low code, simplifying their software architecture's complexity. There are two reasons for embedding a rule engine feature instead of relying on a separate rule engine outside of the broker: diff --git a/en/202305/how-to-use-mqtt-in-nodejs.md b/en/202305/how-to-use-mqtt-in-nodejs.md index b74c5309..55d33346 100644 --- a/en/202305/how-to-use-mqtt-in-nodejs.md +++ b/en/202305/how-to-use-mqtt-in-nodejs.md @@ -52,7 +52,7 @@ Before proceeding, please ensure you have an MQTT broker to communicate and test - **Private deployment** - [EMQX](https://www.emqx.io/) is the most scalable open-source MQTT broker for IoT, [IIoT](https://www.emqx.com/en/blog/iiot-explained-examples-technologies-benefits-and-challenges), and connected vehicles. You can run the following Docker command to install EMQX. + [EMQX](https://github.com/emqx/emqx) is the most scalable open-source MQTT broker for IoT, [IIoT](https://www.emqx.com/en/blog/iiot-explained-examples-technologies-benefits-and-challenges), and connected vehicles. You can run the following Docker command to install EMQX. ```apache docker run -d --name emqx -p 1883:1883 -p 8083:8083 -p 8084:8084 -p 8883:8883 -p 18083:18083 emqx/emqx diff --git a/en/202305/mqtt-broker-clustering.md b/en/202305/mqtt-broker-clustering.md index d88cb235..5e145e67 100644 --- a/en/202305/mqtt-broker-clustering.md +++ b/en/202305/mqtt-broker-clustering.md @@ -6,7 +6,7 @@ If you're involved in the IoT (Internet of Things) space or have embarked on any Today, we are going to introduce the key aspect of MQTT, one that's crucial for large-scale IoT deployments - MQTT broker clustering. -This series is not merely a discourse on [EMQX](https://www.emqx.io/); instead, it's an attempt to comprehensively explore current MQTT technologies. We aim to provide insights, stimulate discussion, and hopefully, ignite a spark of innovation in your journey with MQTT and IoT. So, stay tuned as we navigate the fascinating landscape of MQTT broker clustering. +This series is not merely a discourse on [EMQX](https://github.com/emqx/emqx); instead, it's an attempt to comprehensively explore current MQTT technologies. We aim to provide insights, stimulate discussion, and hopefully, ignite a spark of innovation in your journey with MQTT and IoT. So, stay tuned as we navigate the fascinating landscape of MQTT broker clustering. ## What is MQTT Broker, and Cluster? diff --git a/en/202305/mqtt-js-tutorial.md b/en/202305/mqtt-js-tutorial.md index e69b71e6..c5056d02 100644 --- a/en/202305/mqtt-js-tutorial.md +++ b/en/202305/mqtt-js-tutorial.md @@ -54,7 +54,7 @@ Before proceeding, ensure that you have an [MQTT broker](https://www.emqx.com/en - **Private deployment** - [EMQX](https://www.emqx.io/) is the most scalable open-source MQTT broker for IoT, [IIoT](https://www.emqx.com/en/blog/iiot-explained-examples-technologies-benefits-and-challenges), and connected vehicles. To install EMQX, run the following Docker command: + [EMQX](https://github.com/emqx/emqx) is the most scalable open-source MQTT broker for IoT, [IIoT](https://www.emqx.com/en/blog/iiot-explained-examples-technologies-benefits-and-challenges), and connected vehicles. To install EMQX, run the following Docker command: ``` docker run -d --name emqx -p 1883:1883 -p 8083:8083 -p 8084:8084 -p 8883:8883 -p 18083:18083 emqx/emqx diff --git a/en/202305/natural-interactions-in-iot-combining-mqtt-and-chatgpt.md b/en/202305/natural-interactions-in-iot-combining-mqtt-and-chatgpt.md index 64134acf..be1d9362 100644 --- a/en/202305/natural-interactions-in-iot-combining-mqtt-and-chatgpt.md +++ b/en/202305/natural-interactions-in-iot-combining-mqtt-and-chatgpt.md @@ -24,11 +24,11 @@ As mentioned earlier, the MQTT protocol is a lightweight messaging protocol that > To learn more about MQTT please refer to [MQTT Protocol Explained: The Basics and a Quick Tutorial](https://www.emqx.com/en/blog/the-easiest-guide-to-getting-started-with-mqtt) -The [MQTT broker](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison) is the key component for connecting many IoT devices using the MQTT protocol. We will use [EMQX](https://www.emqx.io/), a highly scalable MQTT broker, in our solution to ensure efficient and reliable connection of massive IoT devices and real-time handling and delivery of message and event stream data. +The [MQTT broker](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison) is the key component for connecting many IoT devices using the MQTT protocol. We will use [EMQX](https://github.com/emqx/emqx), a highly scalable MQTT broker, in our solution to ensure efficient and reliable connection of massive IoT devices and real-time handling and delivery of message and event stream data. > The world's most scalable MQTT Broker for IoT > -> For more information please refer to [EMQX](https://www.emqx.io/) +> For more information please refer to [EMQX](https://github.com/emqx/emqx) We can use an [MQTT client](https://www.emqx.com/en/blog/mqtt-client-tools) to connect to the MQTT broker and communicate with IoT devices. In this blog, we use [MQTTX](https://mqttx.app), a cross-platform open-source MQTT client that provides desktop, command line, and web-based applications. It can test the connection with MQTT brokers and help developers quickly develop and debug MQTT services and applications. @@ -223,7 +223,7 @@ In the future, we can imagine ChatGPT or smarter AGI tools having more of a role ## Conclusion -This blog delves deep into the integration of MQTT and ChatGPT, revealing the exciting possibilities they offer in various applications. By utilizing [EMQX](https://www.emqx.io/), [MQTTX](https://mqttx.app/), and the OpenAI API, we explore implementing an AI application similar to ChatGPT. Through seamless data reception and forwarding via MQTT, we successfully demonstrate the integration of MQTT and ChatGPT. +This blog delves deep into the integration of MQTT and ChatGPT, revealing the exciting possibilities they offer in various applications. By utilizing [EMQX](https://github.com/emqx/emqx), [MQTTX](https://mqttx.app/), and the OpenAI API, we explore implementing an AI application similar to ChatGPT. Through seamless data reception and forwarding via MQTT, we successfully demonstrate the integration of MQTT and ChatGPT. As AI technology becomes more integrated into products (such as New Bing using GPT models for search engines and GitHub's Copilot), we think that the future trends of AI and IoT technologies will also involve enhancing natural language interactions, making device control smarter, and creating more novel use cases. These technologies are not yet part of the production environment but are on the horizon. diff --git a/en/202305/one-click-deploying-emqx-mqtt-broker-on-aws-using-terraform.md b/en/202305/one-click-deploying-emqx-mqtt-broker-on-aws-using-terraform.md index 6b4e399c..86776466 100644 --- a/en/202305/one-click-deploying-emqx-mqtt-broker-on-aws-using-terraform.md +++ b/en/202305/one-click-deploying-emqx-mqtt-broker-on-aws-using-terraform.md @@ -1,6 +1,6 @@ ## Introduction -[MQTT](https://www.emqx.com/en/mqtt-guide) is a lightweight messaging protocol commonly used in IoT (Internet of Things) applications to enable communication between devices. As a [popular open-source MQTT broker, EMQX](https://www.emqx.io/) provides high scalability, reliability, and security for MQTT messaging. +[MQTT](https://www.emqx.com/en/mqtt-guide) is a lightweight messaging protocol commonly used in IoT (Internet of Things) applications to enable communication between devices. As a [popular open-source MQTT broker, EMQX](https://github.com/emqx/emqx) provides high scalability, reliability, and security for MQTT messaging. By using Terraform, a widespread Infrastructure as Code (IaC) tool, you can automate the deployment of EMQX MQTT Broker on AWS, making it easy to set up and manage your MQTT infrastructure. diff --git a/en/202305/one-click-deploying-emqx-mqtt-broker-on-gcp-using-terraform.md b/en/202305/one-click-deploying-emqx-mqtt-broker-on-gcp-using-terraform.md index 6b16d5c5..807b224f 100644 --- a/en/202305/one-click-deploying-emqx-mqtt-broker-on-gcp-using-terraform.md +++ b/en/202305/one-click-deploying-emqx-mqtt-broker-on-gcp-using-terraform.md @@ -1,6 +1,6 @@ ## Introduction -MQTT is a lightweight messaging protocol commonly used in IoT (Internet of Things) applications to enable communication between devices. As a popular [open-source MQTT broker, EMQX](https://www.emqx.io/) provides high scalability, reliability, and security for MQTT messaging. +MQTT is a lightweight messaging protocol commonly used in IoT (Internet of Things) applications to enable communication between devices. As a popular [open-source MQTT broker, EMQX](https://github.com/emqx/emqx) provides high scalability, reliability, and security for MQTT messaging. By using Terraform, a widespread Infrastructure as Code (IaC) tool, you can automate the deployment of EMQX MQTT Broker on GCP, making it easy to set up and manage your MQTT infrastructure. diff --git a/en/202305/top-3-open-source-mqtt-brokers-for-industrial-iot-in-2023.md b/en/202305/top-3-open-source-mqtt-brokers-for-industrial-iot-in-2023.md index 69f9c715..b59efa54 100644 --- a/en/202305/top-3-open-source-mqtt-brokers-for-industrial-iot-in-2023.md +++ b/en/202305/top-3-open-source-mqtt-brokers-for-industrial-iot-in-2023.md @@ -19,7 +19,7 @@ Here is a summary of the 3 projects hosted on GitHub: | | **EMQX** | **Mosquitto** | **NanoMQ** | | :---------------------------------- | :------------------------------------------ | :------------------------------------------------------- | :---------------------------------------------- | -| **Official Website** | [EMQX](https://www.emqx.io/) | [Eclipse Mosquitto](https://mosquitto.org/) | [NanoMQ](https://nanomq.io/) | +| **Official Website** | [EMQX](https://github.com/emqx/emqx) | [Eclipse Mosquitto](https://mosquitto.org/) | [NanoMQ](https://nanomq.io/) | | **GitHub Project** | [EMQX GitHub](https://github.com/emqx/emqx) | [Mosquitto GitHub](https://github.com/eclipse/mosquitto) | [NanoMQ GitHub](https://github.com/nanomq/nanomq) | | **Project Created** | 2012 | 2009 | 2020 | | **License** | Apache License 2.0 | EPL/EDL License | MIT License | @@ -34,7 +34,7 @@ Here is a summary of the 3 projects hosted on GitHub: ## 1. EMQX -[EMQX](https://www.emqx.io/) is a highly scalable, distributed MQTT broker for enterprise IIoT deployments. It offers extensive support for MQTT 5.0, [MQTT-SN](https://www.emqx.com/en/blog/connecting-mqtt-sn-devices-using-emqx), SSL/TLS encryption, and [MQTT over QUIC](https://www.emqx.com/en/blog/mqtt-over-quic). It further enables masterless clustering to achieve high availability and horizontal scalability. +[EMQX](https://github.com/emqx/emqx) is a highly scalable, distributed MQTT broker for enterprise IIoT deployments. It offers extensive support for MQTT 5.0, [MQTT-SN](https://www.emqx.com/en/blog/connecting-mqtt-sn-devices-using-emqx), SSL/TLS encryption, and [MQTT over QUIC](https://www.emqx.com/en/blog/mqtt-over-quic). It further enables masterless clustering to achieve high availability and horizontal scalability. With an impressive 11.5k stars on GitHub, EMQX has established itself as one of the most [popular MQTT brokers](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison) available. The EMQX project was launched in 2012 and is licensed under Apache version 2.0. EMQX is written in Erlang/OTP, a programming language for building massively scalable soft real-time systems. @@ -159,7 +159,7 @@ The 3 MQTT brokers can work together to build the UNS architecture. A cohesive s ## Conclusion -Based on the earlier introduction and comparison, each MQTT broker offers distinct strengths for different deployment scenarios. [EMQX](https://www.emqx.io/) is highly scalable with enterprise features, suitable for cloud deployment. [Mosquitto](https://mosquitto.org/) and [NanoMQ](https://nanomq.io/) are fast and lightweight, ideal for industrial gateways. +Based on the earlier introduction and comparison, each MQTT broker offers distinct strengths for different deployment scenarios. [EMQX](https://github.com/emqx/emqx) is highly scalable with enterprise features, suitable for cloud deployment. [Mosquitto](https://mosquitto.org/) and [NanoMQ](https://nanomq.io/) are fast and lightweight, ideal for industrial gateways. These three MQTT brokers play a significant role in industrial IoT applications, leading the way in implementing the UNS architecture and facilitating the convergence of IT and OT domains. When considering your specific IIoT projects, you can choose one or two of these MQTT brokers based on your requirements. By leveraging their strengths, you can create a cohesive system where the MQTT brokers work together, synergizing their capabilities. diff --git a/en/202305/using-terraform-to-deploy-emqx-mqtt-broker.md b/en/202305/using-terraform-to-deploy-emqx-mqtt-broker.md index ef0c4e7a..f58d2932 100644 --- a/en/202305/using-terraform-to-deploy-emqx-mqtt-broker.md +++ b/en/202305/using-terraform-to-deploy-emqx-mqtt-broker.md @@ -2,11 +2,11 @@ Modern IoT applications require real-time and efficient communication protocols to manage the constant data flow between devices. One such protocol, MQTT (Message Queuing Telemetry Transport), has gained significant popularity in the IoT landscape due to its lightweight, low bandwidth, and high-performance capabilities. -This blog post will discuss deploying your MQTT infrastructure using [EMQX - a highly scalable MQTT broker](https://www.emqx.io/), and Terraform - an Infrastructure as Code (IaC) tool. +This blog post will discuss deploying your MQTT infrastructure using [EMQX - a highly scalable MQTT broker](https://github.com/emqx/emqx), and Terraform - an Infrastructure as Code (IaC) tool. ## EMQX and Terraform -[EMQX](https://www.emqx.io/) is an open-source distributed MQTT broker that provides robust and scalable messaging services. It can handle millions of concurrent [MQTT connections](https://www.emqx.com/en/blog/how-to-set-parameters-when-establishing-an-mqtt-connection) and is optimized for performance, making it a perfect choice for IoT deployments. +[EMQX](https://github.com/emqx/emqx) is an open-source distributed MQTT broker that provides robust and scalable messaging services. It can handle millions of concurrent [MQTT connections](https://www.emqx.com/en/blog/how-to-set-parameters-when-establishing-an-mqtt-connection) and is optimized for performance, making it a perfect choice for IoT deployments. Terraform is an IaC tool that defines, provides, and manages cloud infrastructure using a declarative language. By adopting Terraform in your MQTT deployments, you can: diff --git a/en/202306/a-deep-dive-into-token-based-authentication-and-oauth-2-0-in-mqtt.md b/en/202306/a-deep-dive-into-token-based-authentication-and-oauth-2-0-in-mqtt.md index 3c34bdfe..2712bf18 100644 --- a/en/202306/a-deep-dive-into-token-based-authentication-and-oauth-2-0-in-mqtt.md +++ b/en/202306/a-deep-dive-into-token-based-authentication-and-oauth-2-0-in-mqtt.md @@ -80,7 +80,7 @@ OAuth 2.0 and OpenID Connect can be used as a mechanism for the clients to retri ## Summary -As the world’s leading MQTT broker, [EMQX](https://www.emqx.io/) supports multiple authentication methods including [JWT authentication](https://docs.emqx.com/en/emqx/v5.0/access-control/authn/jwt.html). You can choose HMAC as your signature scheme, or the more secure RSA, or directly configure a JWKS endpoint for EMQX to enable JWT authentication. +As the world’s leading MQTT broker, [EMQX](https://github.com/emqx/emqx) supports multiple authentication methods including [JWT authentication](https://docs.emqx.com/en/emqx/v5.0/access-control/authn/jwt.html). You can choose HMAC as your signature scheme, or the more secure RSA, or directly configure a JWKS endpoint for EMQX to enable JWT authentication. By adopting these additional authentication approaches, you can strengthen your overall system's defenses against unauthorized access and potential security breaches. As technology continues to evolve, it becomes increasingly vital to stay up-to-date with the latest authentication techniques. diff --git a/en/202306/advanced-features-of-mqtt-topics.md b/en/202306/advanced-features-of-mqtt-topics.md index 7051e82f..86a4ff44 100644 --- a/en/202306/advanced-features-of-mqtt-topics.md +++ b/en/202306/advanced-features-of-mqtt-topics.md @@ -67,7 +67,7 @@ sensor/bedroom/1/temperature The topics starting with `$SYS/` are system topics mainly used to get metadata about the MQTT broker's running status, statistics, client online/offline events, etc. `$SYS/` topic is not defined in the MQTT specification. However, most [MQTT brokers](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison) follow this [recommendation](https://github.com/mqtt/mqtt.org/wiki/SYS-Topics). -For example, the [EMQX](https://www.emqx.io/) supports getting cluster status through the following topics. +For example, the [EMQX](https://github.com/emqx/emqx) supports getting cluster status through the following topics. | Topic | Description | | ------------------------------- | ------------------------ | diff --git a/en/202306/bridging-modbus-data-to-mqtt-for-iiot.md b/en/202306/bridging-modbus-data-to-mqtt-for-iiot.md index a80b7cac..f2853539 100644 --- a/en/202306/bridging-modbus-data-to-mqtt-for-iiot.md +++ b/en/202306/bridging-modbus-data-to-mqtt-for-iiot.md @@ -67,11 +67,11 @@ Therefore, in the field of IoT, MQTT is more suitable for message transmission i The Modbus to MQTT bridging architecture consists of two main components: the Modbus data source and the [MQTT broker](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison). The data source sends Modbus data to the MQTT broker, which then receives and forwards it. To achieve this process, two essential elements are required: an edge device responsible for converting the Modbus protocol into MQTT and transmitting the data to the MQTT broker, and an MQTT broker that handles MQTT messages. -In this article, we use [Neuron](https://neugates.io/) and [EMQX](https://www.emqx.io/) to implement the bridging process. +In this article, we use [Neuron](https://neugates.io/) and [EMQX](https://github.com/emqx/emqx) to implement the bridging process. [Neuron](https://neugates.io/) is a modern [industrial IoT](https://www.emqx.com/en/blog/iiot-explained-examples-technologies-benefits-and-challenges) connectivity server that can connect various industrial devices using standard or proprietary protocols, achieving interconnectivity between industrial IoT platforms and devices. As a lightweight industrial software, Neuron can run on various IoT edge hardware devices with limited resources. It aims to solve the problem of difficult unified access to automation equipment data centered around data and provide basic support for intelligent manufacturing. -[EMQX](https://www.emqx.io/) is the world’s leading open-source distributed IoT MQTT broker with high performance and scalability. EMQX provides efficient and reliable connections for massive IoT devices, enabling high-performance real-time movement and processing of the message and event flow data, helping users quickly build IoT platforms and applications for critical business. +[EMQX](https://github.com/emqx/emqx) is the world’s leading open-source distributed IoT MQTT broker with high performance and scalability. EMQX provides efficient and reliable connections for massive IoT devices, enabling high-performance real-time movement and processing of the message and event flow data, helping users quickly build IoT platforms and applications for critical business. The following diagram shows how Neuron collects data from the edge and converts it into MQTT for uploading to EMQX. @@ -266,7 +266,7 @@ By building an open equipment data network, an oil production plant data center ![Oil Production Data Acquisition](https://assets.emqx.com/images/5c5a23f0474e9305c1f4d0026176f01b.png) -An overall solution combining Neuron and other EMQ products like [EMQX](https://www.emqx.io/), [eKuiper](https://ekuiper.org/) and [EMQX ECP](https://www.emqx.com/en/products/emqx-ecp) can bring the following benefits to oil industry: +An overall solution combining Neuron and other EMQ products like [EMQX](https://github.com/emqx/emqx), [eKuiper](https://ekuiper.org/) and [EMQX ECP](https://www.emqx.com/en/products/emqx-ecp) can bring the following benefits to oil industry: - A system architecture that is light on the frontend and heavy on the backend, reducing field equipment and system operation and maintenance costs. - Improved business system responsiveness through real-time reporting of production data by using the MQTT IoT protocol as the main method of data collection and transmission. diff --git a/en/202306/build-mqtt-dashboard-with-emqx-grafana-and-prometheus.md b/en/202306/build-mqtt-dashboard-with-emqx-grafana-and-prometheus.md index 3985d6af..36c236d5 100644 --- a/en/202306/build-mqtt-dashboard-with-emqx-grafana-and-prometheus.md +++ b/en/202306/build-mqtt-dashboard-with-emqx-grafana-and-prometheus.md @@ -2,7 +2,7 @@ EMQX is the world’s leading open-source distributed [MQTT broker](https://www. > EMQX GitHub: [https://github.com/emqx/emqx](https://github.com/emqx/emqx) -In this article, we will introduce how to build an MQTT Dashboard to monitor [EMQX 5.0](https://www.emqx.io/) with Prometheus and use Grafana to visualize its data metrics. In addition, we will introduce [EMQX Exporter](https://github.com/emqx/emqx-exporter) to expose metrics that are not included in the Prometheus API. It is compatible with EMQX 4.4 and EMQX 5, both open-source and enterprise. +In this article, we will introduce how to build an MQTT Dashboard to monitor [EMQX 5.0](https://github.com/emqx/emqx) with Prometheus and use Grafana to visualize its data metrics. In addition, we will introduce [EMQX Exporter](https://github.com/emqx/emqx-exporter) to expose metrics that are not included in the Prometheus API. It is compatible with EMQX 4.4 and EMQX 5, both open-source and enterprise. ## Build a Powerful MQTT Dashboard diff --git a/en/202306/connect-to-mqtt-broker-with-websocket.md b/en/202306/connect-to-mqtt-broker-with-websocket.md index 95148e94..b7a9f344 100644 --- a/en/202306/connect-to-mqtt-broker-with-websocket.md +++ b/en/202306/connect-to-mqtt-broker-with-websocket.md @@ -295,7 +295,7 @@ Yes, you can use MQTT over WebSocket in non-browser environments. Different prog ### Why do I need to fill in a path when connecting to EMQX? -A path must be filled in when using WebSocket to connect to [EMQX](https://www.emqx.io/). This is because EMQX follows the unified path specification of MQTT-WebSocket. This specification requires a specific path to be specified in WebSocket connections to identify and distinguish MQTT over WebSocket traffic. This path routes MQTT over WebSocket traffic to the MQTT Broker for processing. +A path must be filled in when using WebSocket to connect to [EMQX](https://github.com/emqx/emqx). This is because EMQX follows the unified path specification of MQTT-WebSocket. This specification requires a specific path to be specified in WebSocket connections to identify and distinguish MQTT over WebSocket traffic. This path routes MQTT over WebSocket traffic to the MQTT Broker for processing. In EMQX, the default path for MQTT over WebSocket is `/mqtt`. This is set according to the specification. Therefore, when connecting to EMQX, this path must be included in the WebSocket address to ensure the connection is correctly routed to the MQTT broker. diff --git a/en/202306/enabling-mqtt-over-quic-on-kubernetes-with-emqx-5-0.md b/en/202306/enabling-mqtt-over-quic-on-kubernetes-with-emqx-5-0.md index 259b626e..3dd96432 100644 --- a/en/202306/enabling-mqtt-over-quic-on-kubernetes-with-emqx-5-0.md +++ b/en/202306/enabling-mqtt-over-quic-on-kubernetes-with-emqx-5-0.md @@ -1,6 +1,6 @@ ## Introduction -[MQTT over QUIC](https://www.emqx.com/en/blog/getting-started-with-mqtt-over-quic-from-scratch), introduced by the world’s leading open-source distributed [MQTT broker, EMQX 5.0](https://www.emqx.io/), combines the advantages of the [MQTT protocol](https://www.emqx.com/en/blog/the-easiest-guide-to-getting-started-with-mqtt) with the characteristics of [QUIC](https://www.emqx.com/en/blog/quic-protocol-the-features-use-cases-and-impact-for-iot-iov). By leveraging QUIC's low connection overhead and multi-path support, MQTT over QUIC offers a promising solution to improve user experience in weak networks and irregular network paths. It can address connection interruptions and slow establishment in IoT scenarios such as connected vehicles operating in challenging environments like mountainous areas or tunnels. +[MQTT over QUIC](https://www.emqx.com/en/blog/getting-started-with-mqtt-over-quic-from-scratch), introduced by the world’s leading open-source distributed [MQTT broker, EMQX 5.0](https://github.com/emqx/emqx), combines the advantages of the [MQTT protocol](https://www.emqx.com/en/blog/the-easiest-guide-to-getting-started-with-mqtt) with the characteristics of [QUIC](https://www.emqx.com/en/blog/quic-protocol-the-features-use-cases-and-impact-for-iot-iov). By leveraging QUIC's low connection overhead and multi-path support, MQTT over QUIC offers a promising solution to improve user experience in weak networks and irregular network paths. It can address connection interruptions and slow establishment in IoT scenarios such as connected vehicles operating in challenging environments like mountainous areas or tunnels. With the continuous development of cloud native, more and more users deploy EMQX clusters on Kubernetes to enjoy the rapid creation and convenient management. This article will introduce how to deploy EMQX clusters on Kubernetes and enable MQTT over QUIC. diff --git a/en/202306/fortifying-mqtt-communication-security-with-ssl-tls.md b/en/202306/fortifying-mqtt-communication-security-with-ssl-tls.md index e40190a0..3b824987 100644 --- a/en/202306/fortifying-mqtt-communication-security-with-ssl-tls.md +++ b/en/202306/fortifying-mqtt-communication-security-with-ssl-tls.md @@ -85,7 +85,7 @@ Implementing TLS requires careful planning and execution to ensure communication TLS provides a secure way to communicate over the Internet. Using a dedicated secret per device and choosing the correct authentication method can enhance the security of TLS. By following the implementation best practices provided in this blog, you can leverage the full power of TLS to build a more secure IoT platform. -[EMQX](https://www.emqx.io/) has built-in support for TLS/SSL, including one-way/two-ways authentication, the X.509 certificate, load balance SSL and many other security certifications. You can enable SSL/TLS for all protocols supported by EMQX and configure the HTTP API provided by EMQX to use TLS. For more guidance, continue exploring what EMQX has to offer: +[EMQX](https://github.com/emqx/emqx) has built-in support for TLS/SSL, including one-way/two-ways authentication, the X.509 certificate, load balance SSL and many other security certifications. You can enable SSL/TLS for all protocols supported by EMQX and configure the HTTP API provided by EMQX to use TLS. For more guidance, continue exploring what EMQX has to offer: - [Enabling one-way authentication for EMQX Enterprise](https://www.emqx.com/en/blog/emqx-server-ssl-tls-secure-connection-configuration-guide) - [Enabling two-way authentication for EMQX Enterprise](https://www.emqx.com/en/blog/enable-two-way-ssl-for-emqx) diff --git a/en/202306/improve-the-reliability-and-security-of-mqtt-broker-with-rate-limit.md b/en/202306/improve-the-reliability-and-security-of-mqtt-broker-with-rate-limit.md index aca39bbe..6166b620 100644 --- a/en/202306/improve-the-reliability-and-security-of-mqtt-broker-with-rate-limit.md +++ b/en/202306/improve-the-reliability-and-security-of-mqtt-broker-with-rate-limit.md @@ -64,7 +64,7 @@ Therefore, the server needs to identify and respond to these potential security Rate limit can prevent attackers from maliciously consuming server resources and affecting service reliability by restricting and balancing traffic. It can also handle traffic fluctuations caused by normal business changes. However, some attacks do not require the attacker to send valid requests, which may bypass the rate limit. Therefore, the server side also needs to identify these potential security threats. -[EMQX](https://www.emqx.io/) is a widely used [MQTT Broker](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison) offering high scalability and availability while prioritizing user security. In EMQX, you can easily set different rate limits for each listener and add the specified Client ID or IP to the backlist. For more information, please visit the [Rate Limit](https://docs.emqx.com/zh/emqx/v5.0/rate-limit/rate-limit.html) and [Blacklist](https://docs.emqx.com/zh/emqx/v5.0/access-control/blacklist.html) feature documentation of EMQX. +[EMQX](https://github.com/emqx/emqx) is a widely used [MQTT Broker](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison) offering high scalability and availability while prioritizing user security. In EMQX, you can easily set different rate limits for each listener and add the specified Client ID or IP to the backlist. For more information, please visit the [Rate Limit](https://docs.emqx.com/zh/emqx/v5.0/rate-limit/rate-limit.html) and [Blacklist](https://docs.emqx.com/zh/emqx/v5.0/access-control/blacklist.html) feature documentation of EMQX. diff --git a/en/202306/leveraging-enhanced-authentication-for-mqtt-security.md b/en/202306/leveraging-enhanced-authentication-for-mqtt-security.md index c9f76976..2a9fb5f3 100644 --- a/en/202306/leveraging-enhanced-authentication-for-mqtt-security.md +++ b/en/202306/leveraging-enhanced-authentication-for-mqtt-security.md @@ -71,7 +71,7 @@ If the server's identity is successfully verified, the client can proceed to sub Enhanced authentication provides users with the possibility to introduce more identity verification methods. You can choose authentication methods suitable for your specific needs and further enhance the security of your system. -[EMQX](https://www.emqx.io/), as a widely-used MQTT broker known for its high scalability and availability, has always prioritized ensuring user security. In addition to [password-based authentication](https://docs.emqx.com/en/emqx/v5.0/access-control/authn/pwoverview.html), EMQX also supports Enhanced Authentication. Users can enable SCRAM authentication with EMQX to improve the security level of their MQTT infrastructure. For more information, please refer to: [MQTT 5.0 Enhanced Authentication](https://docs.emqx.com/en/emqx/v5.0/access-control/authn/scram.html#configure-with-dashboard). +[EMQX](https://github.com/emqx/emqx), as a widely-used MQTT broker known for its high scalability and availability, has always prioritized ensuring user security. In addition to [password-based authentication](https://docs.emqx.com/en/emqx/v5.0/access-control/authn/pwoverview.html), EMQX also supports Enhanced Authentication. Users can enable SCRAM authentication with EMQX to improve the security level of their MQTT infrastructure. For more information, please refer to: [MQTT 5.0 Enhanced Authentication](https://docs.emqx.com/en/emqx/v5.0/access-control/authn/scram.html#configure-with-dashboard). diff --git a/en/202306/mqtt-sparkplug-solution-for-industrial-iot-using-emqx-and-neuron.md b/en/202306/mqtt-sparkplug-solution-for-industrial-iot-using-emqx-and-neuron.md index 709b749f..7d90c018 100644 --- a/en/202306/mqtt-sparkplug-solution-for-industrial-iot-using-emqx-and-neuron.md +++ b/en/202306/mqtt-sparkplug-solution-for-industrial-iot-using-emqx-and-neuron.md @@ -2,11 +2,11 @@ Sparkplug is an MQTT-base communication protocol designed specifically for industrial automation and IoT applications. To implement a Sparkplug solution, two essential components must be in place. One is an [MQTT broker](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison) for message distribution and management; the other is an edge node to connect local devices to the broker to enable real-time data processing and analysis. -In this article, we will use [EMQX](https://www.emqx.io/), an open-source distributed MQTT broker, and [Neuron](https://neugates.io/), an edge [IIoT](https://www.emqx.com/en/blog/iiot-explained-examples-technologies-benefits-and-challenges) connectivity server, to provide a scalable and robust platform for building Sparkplug solutions. We will delve into the architecture of Sparkplug solution and the roles that EMQX and Neuron play. +In this article, we will use [EMQX](https://github.com/emqx/emqx), an open-source distributed MQTT broker, and [Neuron](https://neugates.io/), an edge [IIoT](https://www.emqx.com/en/blog/iiot-explained-examples-technologies-benefits-and-challenges) connectivity server, to provide a scalable and robust platform for building Sparkplug solutions. We will delve into the architecture of Sparkplug solution and the roles that EMQX and Neuron play. ## The Role of EMQX -[EMQX](https://www.emqx.io/) is used to create an [MQTT topic](https://www.emqx.com/en/blog/advanced-features-of-mqtt-topics) namespace that conforms to the Sparkplug specification. The Sparkplug namespace defines the structure and content of the MQTT messages that device will publish and subscribe to. EMQX ensures that all messages sent to and received from the Sparkplug namespace are properly formatted and conform to the Sparkplug specification. +[EMQX](https://github.com/emqx/emqx) is used to create an [MQTT topic](https://www.emqx.com/en/blog/advanced-features-of-mqtt-topics) namespace that conforms to the Sparkplug specification. The Sparkplug namespace defines the structure and content of the MQTT messages that device will publish and subscribe to. EMQX ensures that all messages sent to and received from the Sparkplug namespace are properly formatted and conform to the Sparkplug specification. > Learn more about EMQX: [EMQX Enterprise: Enterprise MQTT Platform At Scale](https://www.emqx.com/en/products/emqx) diff --git a/en/202306/mqtt-stream-processing-with-emqx-and-ekuiper.md b/en/202306/mqtt-stream-processing-with-emqx-and-ekuiper.md index fe9309a0..d17ee018 100644 --- a/en/202306/mqtt-stream-processing-with-emqx-and-ekuiper.md +++ b/en/202306/mqtt-stream-processing-with-emqx-and-ekuiper.md @@ -2,7 +2,7 @@ [MQTT protocol](https://www.emqx.com/en/blog/the-easiest-guide-to-getting-started-with-mqtt) is a lightweight messaging protocol that is ideal for IoT applications. It is designed to be simple, open, and easy to implement, making it a popular choice for IoT applications. MQTT data are ingested continuously and in real-time and thus are suitable to be processed by stream processing engines. -As a large-scale distributed [MQTT broker](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison) for IoT, [EMQX](https://www.emqx.io/) can efficiently and reliably connect to massive IoT devices, and process and distribute messages and event flow data in real-time. [eKuiper](https://ekuiper.org/) is an open-source stream processing engine that can filter, transform, and aggregate streaming data. +As a large-scale distributed [MQTT broker](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison) for IoT, [EMQX](https://github.com/emqx/emqx) can efficiently and reliably connect to massive IoT devices, and process and distribute messages and event flow data in real-time. [eKuiper](https://ekuiper.org/) is an open-source stream processing engine that can filter, transform, and aggregate streaming data. This article will demonstrate using eKuiper to stream process MQTT data from EMQX in real-time. diff --git a/en/202306/overcoming-address-change-with-mqtt-over-quic.md b/en/202306/overcoming-address-change-with-mqtt-over-quic.md index 27f4e3a0..097de0f5 100644 --- a/en/202306/overcoming-address-change-with-mqtt-over-quic.md +++ b/en/202306/overcoming-address-change-with-mqtt-over-quic.md @@ -200,7 +200,7 @@ MQTT over QUIC emerged as a powerful solution to address these challenges. By le Through the step-by-step demonstration, we showcased the effectiveness of MQTT over QUIC in handling client address migration. By adopting MQTT over QUIC, developers and organizations can enhance the reliability, scalability, and overall performance of their MQTT-based systems. -As IoT applications continue to evolve in dynamic network environments, MQTT over QUIC proves to be a valuable protocol choice with its ability to handle address migration seamlessly. With the effort of [EMQX](https://www.emqx.io/) as the first MQTT broker that supports MQTT over QUIC, we can expect further advancements in addressing network related challenges and enabling seamless communication in the ever-expanding world of IoT. +As IoT applications continue to evolve in dynamic network environments, MQTT over QUIC proves to be a valuable protocol choice with its ability to handle address migration seamlessly. With the effort of [EMQX](https://github.com/emqx/emqx) as the first MQTT broker that supports MQTT over QUIC, we can expect further advancements in addressing network related challenges and enabling seamless communication in the ever-expanding world of IoT. diff --git a/en/202306/sparkplug-3-0-advancements-and-formalization-in-mqtt-for-iiot.md b/en/202306/sparkplug-3-0-advancements-and-formalization-in-mqtt-for-iiot.md index 34584f10..823462a9 100644 --- a/en/202306/sparkplug-3-0-advancements-and-formalization-in-mqtt-for-iiot.md +++ b/en/202306/sparkplug-3-0-advancements-and-formalization-in-mqtt-for-iiot.md @@ -101,7 +101,7 @@ The program offers benefits to both vendors and customers: Sparkplug 3.0 brings significant advancements and formalization to the MQTT Sparkplug protocol for IIoT applications. With improved clarity, explicit specifications, and alignment with MQTT 5.0, Sparkplug 3.0 offers enhanced interoperability, efficient data synchronization, and streamlined deployment in industrial environments. As the IIoT ecosystem continues to evolve, Sparkplug 3.0 provides a robust and standardized solution for reliable and scalable communication within IIoT networks. -As the world’s leading [open-source MQTT broker, EMQX](https://www.emqx.io/) is the main component of infrastructure to manage all Sparkplug 3.0 message traffic. [Neuron, an IIoT connectivity server](https://neugates.io/), can act as an edge node and assist OT devices to be smarter and to report Sparkplug 3.0 messages in an asynchronous way. +As the world’s leading [open-source MQTT broker, EMQX](https://github.com/emqx/emqx) is the main component of infrastructure to manage all Sparkplug 3.0 message traffic. [Neuron, an IIoT connectivity server](https://neugates.io/), can act as an edge node and assist OT devices to be smarter and to report Sparkplug 3.0 messages in an asynchronous way. diff --git a/en/202306/use-mqtt-with-raspberry-pi.md b/en/202306/use-mqtt-with-raspberry-pi.md index 26d4a33f..b43d5cf4 100644 --- a/en/202306/use-mqtt-with-raspberry-pi.md +++ b/en/202306/use-mqtt-with-raspberry-pi.md @@ -55,7 +55,7 @@ Before proceeding, please ensure you have an MQTT broker to communicate and test - **Private deployment** - [EMQX](https://www.emqx.io/) is the most scalable open-source MQTT broker for IoT, [IIoT](https://www.emqx.com/en/blog/iiot-explained-examples-technologies-benefits-and-challenges), and connected vehicles. You can run the following Docker command to install EMQX. + [EMQX](https://github.com/emqx/emqx) is the most scalable open-source MQTT broker for IoT, [IIoT](https://www.emqx.com/en/blog/iiot-explained-examples-technologies-benefits-and-challenges), and connected vehicles. You can run the following Docker command to install EMQX. ```shell docker run -d --name emqx -p 1883:1883 -p 8083:8083 -p 8084:8084 -p 8883:8883 -p 18083:18083 emqx/emqx diff --git a/en/202306/what-is-the-mqtt-protocol.md b/en/202306/what-is-the-mqtt-protocol.md index bdd6a9a9..079f31f3 100644 --- a/en/202306/what-is-the-mqtt-protocol.md +++ b/en/202306/what-is-the-mqtt-protocol.md @@ -162,7 +162,7 @@ If you want to learn more about MQTT 5.0, you can try reading our [MQTT 5.0 Expl The MQTT broker is responsible for receiving client-initiated connections and forwarding messages sent by the client to some other eligible clients. A mature MQTT broker can support massive connections and millions of messages throughput, helping IoT business providers focus on business functionality and quickly create a reliable MQTT application. -[EMQX](https://www.emqx.io/) is a widely-used large-scale distributed MQTT broker for IoT. Since its open-source release on GitHub in 2013, it has been downloaded by more than 10 million times worldwide and the cumulative number of connected IoT key devices exceeds 100 million. +[EMQX](https://github.com/emqx/emqx) is a widely-used large-scale distributed MQTT broker for IoT. Since its open-source release on GitHub in 2013, it has been downloaded by more than 10 million times worldwide and the cumulative number of connected IoT key devices exceeds 100 million. You can install EMQX 5.0 open-source version with the following Docker command to experience it. diff --git a/en/202307/bridging-twincat-data-to-mqtt.md b/en/202307/bridging-twincat-data-to-mqtt.md index c732f689..7bb4d80b 100644 --- a/en/202307/bridging-twincat-data-to-mqtt.md +++ b/en/202307/bridging-twincat-data-to-mqtt.md @@ -16,7 +16,7 @@ With the Beckhoff ADS plugin, users can collect data from TwinCAT PLCs easily. T ### EMQX for Handling MQTT Messages -[EMQX](https://www.emqx.io/) is the world’s leading open-source distributed IoT [MQTT broker](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison) with high performance and scalability. It provides efficient and reliable connections for massive IoT devices, enabling high-performance real-time movement and processing of the message and event flow data, helping users quickly build IoT platforms and applications for critical business. +[EMQX](https://github.com/emqx/emqx) is the world’s leading open-source distributed IoT [MQTT broker](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison) with high performance and scalability. It provides efficient and reliable connections for massive IoT devices, enabling high-performance real-time movement and processing of the message and event flow data, helping users quickly build IoT platforms and applications for critical business. EMQX is the broker component in the bridging architecture, while Neuron collects data from TwinCAT PLCs and transmits the data in MQTT messages to the broker. After receiving the MQTT messages from Neuron, EMQX will then forward the data or perform further processing. diff --git a/en/202307/embedded-mqtt-message-storage-using-rocksdb-for-emqx-broker.md b/en/202307/embedded-mqtt-message-storage-using-rocksdb-for-emqx-broker.md index 30a90304..b067fec1 100644 --- a/en/202307/embedded-mqtt-message-storage-using-rocksdb-for-emqx-broker.md +++ b/en/202307/embedded-mqtt-message-storage-using-rocksdb-for-emqx-broker.md @@ -1,4 +1,4 @@ -[EMQX](https://www.emqx.io/) is an open-source [MQTT broker](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison) that allows clients to publish and subscribe to data over [MQTT protocol](https://www.emqx.com/en/blog/the-easiest-guide-to-getting-started-with-mqtt). Basic functions of EMQX router keep messages in RAM, which guarantees low latency and high throughput. However, its message delivery guarantees have some limitations. Specifically, if the broker nodes go offline, the messages kept in memory would be lost. This could potentially cause message loss for clients. +[EMQX](https://github.com/emqx/emqx) is an open-source [MQTT broker](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison) that allows clients to publish and subscribe to data over [MQTT protocol](https://www.emqx.com/en/blog/the-easiest-guide-to-getting-started-with-mqtt). Basic functions of EMQX router keep messages in RAM, which guarantees low latency and high throughput. However, its message delivery guarantees have some limitations. Specifically, if the broker nodes go offline, the messages kept in memory would be lost. This could potentially cause message loss for clients. To address this issue and improve reliability, the EMQX team is working on implementing message persistence using an embedded database, RocksDB. This feature will store messages even when broker nodes are offline, thereby ensuring message delivery. diff --git a/en/202307/emqx-mqtt-broker-authentication-troubleshooting.md b/en/202307/emqx-mqtt-broker-authentication-troubleshooting.md index c24c6fb8..320ea1ff 100644 --- a/en/202307/emqx-mqtt-broker-authentication-troubleshooting.md +++ b/en/202307/emqx-mqtt-broker-authentication-troubleshooting.md @@ -1,4 +1,4 @@ ->[EMQX](https://www.emqx.io/) is a popular [MQTT Broker](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison) widely used in the Internet of Things(IoT), Industrial IoT ([IIoT](https://www.emqx.com/en/blog/iiot-explained-examples-technologies-benefits-and-challenges)) and Connected Cars. It can connect millions of devices at scale, move and process your IoT data in real-time anywhere with high performance, scalability and reliability. +>[EMQX](https://github.com/emqx/emqx) is a popular [MQTT Broker](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison) widely used in the Internet of Things(IoT), Industrial IoT ([IIoT](https://www.emqx.com/en/blog/iiot-explained-examples-technologies-benefits-and-challenges)) and Connected Cars. It can connect millions of devices at scale, move and process your IoT data in real-time anywhere with high performance, scalability and reliability. > >In this blog series, we will explore common troubleshooting scenarios when using EMQX and provide practical tips and solutions to overcome them. Readers can optimize your MQTT deployment and ensure smooth communication between your devices following this troubleshooting instruction. diff --git a/en/202307/time-series-database-for-iot-the-missing-piece.md b/en/202307/time-series-database-for-iot-the-missing-piece.md index b84cd798..148d1d91 100644 --- a/en/202307/time-series-database-for-iot-the-missing-piece.md +++ b/en/202307/time-series-database-for-iot-the-missing-piece.md @@ -69,7 +69,7 @@ Many use cases demonstrate the versatility and power of integrating MQTT with TS ## How EMQX Enables Easy Integration of Time-Series Databases with MQTT -[EMQX](https://www.emqx.io/), provider of a [popular MQTT broker](https://www.emqx.com/en/mqtt/public-mqtt5-broker), can seamlessly integrate with various TSDBs, such as Timescale, InfluxDB, and Apache IoTDB, making them compatible with various IoT frameworks and tools. This integration facilitates smooth data flow from Industry IoT devices to TSDB, streamlines data processing pipelines, and simplifies Industry IoT data management architecture. +[EMQX](https://github.com/emqx/emqx), provider of a [popular MQTT broker](https://www.emqx.com/en/mqtt/public-mqtt5-broker), can seamlessly integrate with various TSDBs, such as Timescale, InfluxDB, and Apache IoTDB, making them compatible with various IoT frameworks and tools. This integration facilitates smooth data flow from Industry IoT devices to TSDB, streamlines data processing pipelines, and simplifies Industry IoT data management architecture. ![Easy Integration of Time-Series Databases with MQTT](https://assets.emqx.com/images/5b34d4ed43c44eb0c9c379a13c1a9686.png) diff --git a/en/202308/bridging-opc-ua-data-to-mqtt-for-iiot.md b/en/202308/bridging-opc-ua-data-to-mqtt-for-iiot.md index 07542fbe..5f792c72 100644 --- a/en/202308/bridging-opc-ua-data-to-mqtt-for-iiot.md +++ b/en/202308/bridging-opc-ua-data-to-mqtt-for-iiot.md @@ -4,7 +4,7 @@ In this blog, we will offer a bridging solution from [OPC UA](https://www.emqx.c [Neuron](https://neugates.io/) is a modern [industrial IoT](https://www.emqx.com/en/blog/iiot-explained-examples-technologies-benefits-and-challenges) connectivity server that can connect to a wide range of industrial devices using standard or device-proprietary protocols, enabling the interconnection of [industrial IoT platforms](https://www.emqx.com/en/blog/iiot-platform-key-components-and-5-notable-solutions) with massive devices. As a lightweight industrial protocol gateway software, Neuron is designed to operate on various IoT edge hardware devices with limited resources. Its primary goal is to address the challenge of accessing data from data-centric automation equipment in a unified manner, thus offering essential support for smart manufacturing. -[EMQX](https://www.emqx.io/) is a distributed open-source [MQTT broker](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison). As the world's most scalable MQTT messaging server, EMQX provides efficient and reliable connectivity to a massive number of IoT devices, enabling high-performance, real-time movement and processing of messages and event streams, helping users rapidly build business-critical IoT platforms and applications. +[EMQX](https://github.com/emqx/emqx) is a distributed open-source [MQTT broker](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison). As the world's most scalable MQTT messaging server, EMQX provides efficient and reliable connectivity to a massive number of IoT devices, enabling high-performance, real-time movement and processing of messages and event streams, helping users rapidly build business-critical IoT platforms and applications. OPC UA data sources can be captured and aggregated by Neuron's southbound OPC UA driver, converted to the MQTT protocol, and transmitted to the EMQX MQTT Broker. The latter then distributes them to various distributed applications. diff --git a/en/202308/emqx-mqtt-broker-troubleshooting-publish-subscribe-issues.md b/en/202308/emqx-mqtt-broker-troubleshooting-publish-subscribe-issues.md index 879f518d..91d42999 100644 --- a/en/202308/emqx-mqtt-broker-troubleshooting-publish-subscribe-issues.md +++ b/en/202308/emqx-mqtt-broker-troubleshooting-publish-subscribe-issues.md @@ -1,4 +1,4 @@ -> [EMQX](https://www.emqx.io/) *is a popular* [MQTT Broker](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison) *widely used in the Internet of Things(IoT), Industrial IoT (*[IIoT](https://www.emqx.com/en/blog/iiot-explained-examples-technologies-benefits-and-challenges)*) and Connected Cars. It can connect millions of devices at scale, move and process your IoT data in real-time anywhere with high performance, scalability and reliability.* +> [EMQX](https://github.com/emqx/emqx) *is a popular* [MQTT Broker](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison) *widely used in the Internet of Things(IoT), Industrial IoT (*[IIoT](https://www.emqx.com/en/blog/iiot-explained-examples-technologies-benefits-and-challenges)*) and Connected Cars. It can connect millions of devices at scale, move and process your IoT data in real-time anywhere with high performance, scalability and reliability.* > > In this blog series, we will explore common troubleshooting scenarios when using EMQX and provide practical tips and solutions to overcome them. Readers can optimize your MQTT deployment and ensure smooth communication between your devices following this troubleshooting instruction . diff --git a/en/202308/emqx-single-node-supports-5m-connections.md b/en/202308/emqx-single-node-supports-5m-connections.md index a7a94e03..8aa582ad 100644 --- a/en/202308/emqx-single-node-supports-5m-connections.md +++ b/en/202308/emqx-single-node-supports-5m-connections.md @@ -18,7 +18,7 @@ Machine Details: | Service | Deployment | Version | OS | CPU | Memory | Cloud Host model | | :--------------------------- | :---------- | :------ | :------- | :--- | :----- | :--------------- | -| [EMQX](https://www.emqx.io/) | single node | 5.0.21 | RHEL 8.5 | 64C | 128G | hfc6.16xlarge | +| [EMQX](https://github.com/emqx/emqx) | single node | 5.0.21 | RHEL 8.5 | 64C | 128G | hfc6.16xlarge | ## Test Tool diff --git a/en/202308/iiot-explained-examples-technologies-benefits-and-challenges.md b/en/202308/iiot-explained-examples-technologies-benefits-and-challenges.md index ca8f01d1..01617bee 100644 --- a/en/202308/iiot-explained-examples-technologies-benefits-and-challenges.md +++ b/en/202308/iiot-explained-examples-technologies-benefits-and-challenges.md @@ -161,7 +161,7 @@ To address this challenge, businesses need to invest in training and development EMQ provides [Neuron](https://www.emqx.com/en/products/neuronex), a lightweight connectivity server for industrial dataops and data-centric automation, tightly integrated with our industry-leading MQTT broker. Neuron provides several significant benefits for IIoT, simplifying connectivity, enhancing data integration, and enabling real-time communication and analytics. -If you are a managing an IIoT deployment, [EMQX](https://www.emqx.io/) and [Neuron](https://www.emqx.com/en/products/neuronex) can help with: +If you are a managing an IIoT deployment, [EMQX](https://github.com/emqx/emqx) and [Neuron](https://www.emqx.com/en/products/neuronex) can help with: 1. **IT Connectivity:** EMQX broker offers a wide range of data bridges, facilitating seamless integration with over 40 cloud services and enterprise systems. This enables instant access to data across diverse applications, reducing the cost and complexity of custom bridge development. EMQX supports integration with popular databases like [MySQL](https://www.emqx.com/en/blog/mqtt-to-mysql), [PostgreSQL](https://www.emqx.com/en/blog/build-an-iot-time-series-data-application-for-energy-storage-with-mqtt-and-timescale), [MongoDB](https://www.emqx.com/en/blog/mqtt-and-mongodb-crafting-seamless-synergy-for-iot-data-mangement), and more, as well as technologies like [Redis](https://www.emqx.com/en/blog/mqtt-and-redis), Oracle, SAP, and [Kafka](https://www.emqx.com/en/blog/mqtt-and-kafka). This rich set of connectors ensures efficient IT connectivity and data exchange within the IIoT ecosystem. 2. **OT Connectivity:** Neuron serves as a protocol gateway, providing a comprehensive set of industrial connectivity options essential for successful IIoT deployments. With support for over 30 industrial protocols such as [Modbus](https://www.emqx.com/en/blog/modbus-protocol-the-grandfather-of-iot-communication), Ethernet/IP, Profinet I/O, OPC-UA, IEC104, [BACnet](https://www.emqx.com/en/blog/bacnet-protocol-basic-concepts-structure-obejct-model-explained), and more, Neuron enables seamless communication with various devices and systems across the operational technology (OT) landscape. Whether it's PLCs, building automation systems, CNC machines, or robotics, Neuron offers a powerful range of drivers to ensure reliable OT connectivity and data acquisition. diff --git a/en/202308/iot-in-the-cloud-8-key-benefits-and-how-to-get-started.md b/en/202308/iot-in-the-cloud-8-key-benefits-and-how-to-get-started.md index 9b1477e6..daf0e19e 100644 --- a/en/202308/iot-in-the-cloud-8-key-benefits-and-how-to-get-started.md +++ b/en/202308/iot-in-the-cloud-8-key-benefits-and-how-to-get-started.md @@ -51,7 +51,7 @@ Choosing the right platform for IoT in the Cloud can significantly simplify the ### EMQX -[EMQX](https://www.emqx.io/) is an open-source IoT platform designed for high-performance and large-scale IoT applications. Its broker is fully compatible with MQTT, a lightweight messaging protocol designed for IoT, ensuring efficient communication between devices and the cloud. Additionally, it provides robust security features, including SSL/TLS encryption and secure device authentication, ensuring data security and privacy. +[EMQX](https://github.com/emqx/emqx) is an open-source IoT platform designed for high-performance and large-scale IoT applications. Its broker is fully compatible with MQTT, a lightweight messaging protocol designed for IoT, ensuring efficient communication between devices and the cloud. Additionally, it provides robust security features, including SSL/TLS encryption and secure device authentication, ensuring data security and privacy. EMQX is available as a fully managed service in the cloud: **[Learn more about EMQX Cloud](https://www.emqx.com/en/cloud)** diff --git a/en/202308/simulating-the-future-crafting-iot-scenarios-with-chatgpt-and-mqttx.md b/en/202308/simulating-the-future-crafting-iot-scenarios-with-chatgpt-and-mqttx.md index 9e67905d..b805ca7a 100644 --- a/en/202308/simulating-the-future-crafting-iot-scenarios-with-chatgpt-and-mqttx.md +++ b/en/202308/simulating-the-future-crafting-iot-scenarios-with-chatgpt-and-mqttx.md @@ -22,7 +22,7 @@ We're pioneering a transformative approach for real-time MQTT data testing in Io 2. **Using ChatGPT to Generate Simulation Scripts:** Based on our assessment, we employ ChatGPT, an advanced large language model, to craft simulation scripts for MQTTX. This not only significantly simplifies script creation but also ensures the quality and authenticity of the data content. -3. **Simulating Data Transmission with MQTTX:** Using scripts generated by ChatGPT, MQTTX simulates device data transmissions, interacting with MQTT servers like [EMQX](https://www.emqx.io). +3. **Simulating Data Transmission with MQTTX:** Using scripts generated by ChatGPT, MQTTX simulates device data transmissions, interacting with MQTT servers like [EMQX](https://github.com/emqx/emqx). ![Incorporating Generative AI into MQTT Data Testing](https://assets.emqx.com/images/f6980406bc52b273f7a6c5b60eed54a4.png) @@ -32,7 +32,7 @@ Core components involved in our methodology: - [MQTTX](https://mqttx.app)**:** A full-featured MQTT client tool, MQTTX boasts a custom script feature, enabling device simulation for message transmission and reception. -- [EMQX](https://www.emqx.io)**:** Our preferred MQTT server, ensuring the stable transmission of simulated data. +- [EMQX](https://github.com/emqx/emqx)**:** Our preferred MQTT server, ensuring the stable transmission of simulated data. In the subsequent sections, we'll guide you on how to kickstart your data simulation testing. diff --git a/en/202309/demonstrate-mqtt-5-0-features-using-mqttx-cli.md b/en/202309/demonstrate-mqtt-5-0-features-using-mqttx-cli.md index d1c8d691..6a91f8c7 100644 --- a/en/202309/demonstrate-mqtt-5-0-features-using-mqttx-cli.md +++ b/en/202309/demonstrate-mqtt-5-0-features-using-mqttx-cli.md @@ -1,6 +1,6 @@ As the most popular communication protocol in the Internet of Things (IoT) field, the latest version of MQTT has already reached 5.0 in 2019. Compared with previous versions, 5.0 has added features more in line with modern IoT application requirements, such as session expiry, reason codes, shared subscriptions, request-response, etc., making it the preferred version for the majority of IoT companies. -To give you a more comprehensive understanding of MQTT 5.0, this article will introduce each new feature introduced in 5.0 in turn, and use the [MQTTX CLI](https://mqttx.app/) tool to demonstrate how we can use these features in [EMQX](https://www.emqx.io/). You can easily run the examples in this article by copying and pasting commands. +To give you a more comprehensive understanding of MQTT 5.0, this article will introduce each new feature introduced in 5.0 in turn, and use the [MQTTX CLI](https://mqttx.app/) tool to demonstrate how we can use these features in [EMQX](https://github.com/emqx/emqx). You can easily run the examples in this article by copying and pasting commands. Before we start, we need to complete the following preparations: diff --git a/en/202309/home-assistant-and-mqtt-4-things-you-could-build.md b/en/202309/home-assistant-and-mqtt-4-things-you-could-build.md index 02080532..4264b353 100644 --- a/en/202309/home-assistant-and-mqtt-4-things-you-could-build.md +++ b/en/202309/home-assistant-and-mqtt-4-things-you-could-build.md @@ -74,7 +74,7 @@ You should have a regular patch management process in place, ensuring that all y ### Installing an MQTT Broker: EMQX -The first step in integrating MQTT with Home Assistant is to install an MQTT Broker. We’ll use [EMQX](https://www.emqx.io/), an open-source, scalable, and highly performant MQTT Broker designed for IoT applications. +The first step in integrating MQTT with Home Assistant is to install an MQTT Broker. We’ll use [EMQX](https://github.com/emqx/emqx), an open-source, scalable, and highly performant MQTT Broker designed for IoT applications. To install EMQX, first, [download the latest version](https://www.emqx.com/en/try?product=broker) and follow the installation instructions. The installation process varies depending on the operating system you are using. For instance, if you are using a Debian-based Linux distribution like Ubuntu, you can install EMQX by executing `sudo apt-get install emqx` in the terminal. diff --git a/en/202309/mqtt-5-0-control-packets-06-auth.md b/en/202309/mqtt-5-0-control-packets-06-auth.md index 2401eef6..c5c0f45f 100644 --- a/en/202309/mqtt-5-0-control-packets-06-auth.md +++ b/en/202309/mqtt-5-0-control-packets-06-auth.md @@ -57,7 +57,7 @@ Now, we have introduced all types of control packets in MQTT. As a binary protoc When we encounter problems, we can first check the Reason Code in the response packet returned by the other party, which can indicate most of the error causes. When some embedded device end-side SDK implementations are poor and cannot directly provide a Reason Code, we can try packet sniffing to view the Reason Code in the packet. At this time, we can use Wireshark to avoid manual parsing. -[EMQX](https://www.emqx.io/), as a widely used, highly scalable MQTT Broker, also provides a [Log Trace](https://docs.emqx.com/en/emqx/v5.1/observability/tracer.html) feature that is convenient for users to troubleshoot problems. It can record all relevant logs of specified Client ID, topic, and IP, including packet receiving and sending logs. So we can use it to analyze whether the behavior of the client is abnormal, such as whether it correctly responded to PUBACK, whether it repeatedly sent CONNACK packets, etc. +[EMQX](https://github.com/emqx/emqx), as a widely used, highly scalable MQTT Broker, also provides a [Log Trace](https://docs.emqx.com/en/emqx/v5.1/observability/tracer.html) feature that is convenient for users to troubleshoot problems. It can record all relevant logs of specified Client ID, topic, and IP, including packet receiving and sending logs. So we can use it to analyze whether the behavior of the client is abnormal, such as whether it correctly responded to PUBACK, whether it repeatedly sent CONNACK packets, etc.
diff --git a/en/202310/emq-intel-and-sjtu-explore-mqtt-over-quic-together.md b/en/202310/emq-intel-and-sjtu-explore-mqtt-over-quic-together.md index 999f5a55..f6d803b8 100644 --- a/en/202310/emq-intel-and-sjtu-explore-mqtt-over-quic-together.md +++ b/en/202310/emq-intel-and-sjtu-explore-mqtt-over-quic-together.md @@ -70,7 +70,7 @@ In the MQTT over QUIC bridging technology topic, Fengping Sun from Shanghai Jiao ### EMQ -EMQ is the world's leading software provider of open-source IoT data infrastructure. The core product portfolio used in this course consists of [EMQX](https://www.emqx.io/), the world’s most scalable and reliable open-source MQTT messaging platform, available in both open-source and commercial versions, and [NanoMQ](https://nanomq.io), an ultra-lightweight MQTT middleware that can run at the edge. They offer a one-stop, cloud-native solution that can connect, move, process, and integrate real-time IoT data from edge to cloud to multi-cloud. +EMQ is the world's leading software provider of open-source IoT data infrastructure. The core product portfolio used in this course consists of [EMQX](https://github.com/emqx/emqx), the world’s most scalable and reliable open-source MQTT messaging platform, available in both open-source and commercial versions, and [NanoMQ](https://nanomq.io), an ultra-lightweight MQTT middleware that can run at the edge. They offer a one-stop, cloud-native solution that can connect, move, process, and integrate real-time IoT data from edge to cloud to multi-cloud. Founded in 2017, EMQ has rapidly grown. Its flagship product, EMQX, has served over 500 enterprise users in more than 50 countries, connecting to a staggering 250 million IoT devices globally. diff --git a/en/202310/iiot-vs-iot-examples-and-5-key-differences.md b/en/202310/iiot-vs-iot-examples-and-5-key-differences.md index ddc6ee51..06334778 100644 --- a/en/202310/iiot-vs-iot-examples-and-5-key-differences.md +++ b/en/202310/iiot-vs-iot-examples-and-5-key-differences.md @@ -116,7 +116,7 @@ Remember, though, that IIoT vs. IoT isn't necessarily an either/or decision. Man EMQ provides [Neuron](https://neugates.io/), a lightweight connectivity server for industrial dataops and data-centric automation, tightly integrated with our industry-leading MQTT broker. Neuron provides several significant benefits for IIoT, simplifying connectivity, enhancing data integration, and enabling real-time communication and analytics. -If you are a managing an IIoT deployment, [EMQX](https://www.emqx.io/) and [Neuron](https://neugates.io/) can help with: +If you are a managing an IIoT deployment, [EMQX](https://github.com/emqx/emqx) and [Neuron](https://neugates.io/) can help with: 1. **IT Connectivity:** EMQX broker offers a wide range of data bridges, facilitating seamless integration with over 40 cloud services and enterprise systems. This enables instant access to data across diverse applications, reducing the cost and complexity of custom bridge development. EMQX supports integration with popular databases like MySQL, PostgreSQL, MongoDB, and more, as well as technologies like Redis, Oracle, SAP, and Kafka. This rich set of connectors ensures efficient IT connectivity and data exchange within the IIoT ecosystem. 2. **OT Connectivity:** Neuron serves as a protocol gateway, providing a comprehensive set of industrial connectivity options essential for successful IIoT deployments. With support for over 30 industrial protocols such as [Modbus](https://www.emqx.com/en/blog/modbus-protocol-the-grandfather-of-iot-communication), Ethernet/IP, Profinet I/O, [OPC-UA](https://www.emqx.com/en/blog/opc-ua-protocol), IEC104, [BACnet](https://www.emqx.com/en/blog/bacnet-protocol-basic-concepts-structure-obejct-model-explained), and more, Neuron enables seamless communication with various devices and systems across the operational technology (OT) landscape. Whether it's PLCs, building automation systems, CNC machines, or robotics, Neuron offers a powerful range of drivers to ensure reliable OT connectivity and data acquisition. diff --git a/en/202310/industrial-iot-applications.md b/en/202310/industrial-iot-applications.md index ca1ad55b..4ecd4e19 100644 --- a/en/202310/industrial-iot-applications.md +++ b/en/202310/industrial-iot-applications.md @@ -158,7 +158,7 @@ Consider creating a cross-functional IIoT team, with representatives from IT, op EMQ provides [Neuron](https://neugates.io/), a lightweight connectivity server for industrial dataops and data-centric automation, tightly integrated with our industry-leading MQTT broker. Neuron provides several significant benefits for IIoT, simplifying connectivity, enhancing data integration, and enabling real-time communication and analytics. -If you are a managing an IIoT deployment, [EMQX](https://www.emqx.io/) and [Neuron](https://neugates.io/) can help with: +If you are a managing an IIoT deployment, [EMQX](https://github.com/emqx/emqx) and [Neuron](https://neugates.io/) can help with: 1. **IT Connectivity:** EMQX broker offers a wide range of data bridges, facilitating seamless integration with over 40 cloud services and enterprise systems. This enables instant access to data across diverse applications, reducing the cost and complexity of custom bridge development. EMQX supports integration with popular databases like [MySQL](https://www.emqx.com/en/blog/mqtt-to-mysql), [PostgreSQL](https://www.emqx.com/en/blog/build-an-iot-time-series-data-application-for-energy-storage-with-mqtt-and-timescale), [MongoDB](https://www.emqx.com/en/blog/building-a-data-aggregation-platform-with-mqtt-and-mongodb), and more, as well as technologies like [Redis](https://www.emqx.com/en/blog/mqtt-and-redis), Oracle, SAP, and [Kafka](https://www.emqx.com/en/blog/mqtt-and-kafka). This rich set of connectors ensures efficient IT connectivity and data exchange within the IIoT ecosystem. 2. **OT Connectivity:** Neuron serves as a protocol gateway, providing a comprehensive set of industrial connectivity options essential for successful IIoT deployments. With support for over 30 industrial protocols such as [Modbus](https://www.emqx.com/en/blog/modbus-protocol-the-grandfather-of-iot-communication), Ethernet/IP, Profinet I/O, [OPC-UA](https://www.emqx.com/en/blog/opc-ua-protocol), IEC104, [BACnet](https://www.emqx.com/en/blog/bacnet-protocol-basic-concepts-structure-obejct-model-explained), and more, Neuron enables seamless communication with various devices and systems across the operational technology (OT) landscape. Whether it's PLCs, building automation systems, CNC machines, or robotics, Neuron offers a powerful range of drivers to ensure reliable OT connectivity and data acquisition. diff --git a/en/202310/introduction-to-mqtt-5.md b/en/202310/introduction-to-mqtt-5.md index c99f9aa0..9a5ed3a8 100644 --- a/en/202310/introduction-to-mqtt-5.md +++ b/en/202310/introduction-to-mqtt-5.md @@ -64,7 +64,7 @@ This feature is particularly useful in scenarios where you have multiple instanc ## Current Support of Broker and Client SDKs in MQTT 5.0 -The MQTT 5.0 protocol has been well received by the IoT community, and numerous [MQTT brokers](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison) and client Software Development Kits (SDKs) have added support for it. Major MQTT brokers, like [EMQX](https://www.emqx.io/), [Mosquitto](https://www.emqx.com/en/blog/mosquitto-mqtt-broker-pros-cons-tutorial-and-modern-alternatives) and [NanoMQ](https://nanomq.io/), have already implemented MQTT 5.0 features in their platforms, allowing users to leverage the new protocol's benefits. +The MQTT 5.0 protocol has been well received by the IoT community, and numerous [MQTT brokers](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison) and client Software Development Kits (SDKs) have added support for it. Major MQTT brokers, like [EMQX](https://github.com/emqx/emqx), [Mosquitto](https://www.emqx.com/en/blog/mosquitto-mqtt-broker-pros-cons-tutorial-and-modern-alternatives) and [NanoMQ](https://nanomq.io/), have already implemented MQTT 5.0 features in their platforms, allowing users to leverage the new protocol's benefits. On the client SDK front, libraries like Paho, which have a broad user base, have added support for MQTT 5.0. This means developers can now utilize MQTT 5.0 features in their IoT applications. Other examples of client SDKs that support MQTT 5.0 are [MQTT.js](https://www.emqx.com/en/blog/mqtt-js-tutorial) and [MQTTnet](https://www.emqx.com/en/blog/connecting-to-serverless-mqtt-broker-with-mqttnet-in-csharp). diff --git a/en/202310/mqtt5-new-feature-clean-start-and-session-expiry-interval.md b/en/202310/mqtt5-new-feature-clean-start-and-session-expiry-interval.md index 4e310f07..6cdec9fa 100644 --- a/en/202310/mqtt5-new-feature-clean-start-and-session-expiry-interval.md +++ b/en/202310/mqtt5-new-feature-clean-start-and-session-expiry-interval.md @@ -96,7 +96,7 @@ So compared to MQTT 3.1.1, MQTT 5.0 has huge improvements in sessions. In MQTT, we usually refer to sessions whose lifecycle is longer than the network connection as persistent sessions. However, there are some things we need to pay attention to when using persistent sessions. -For example, we need to correctly evaluate the impact of persistent sessions on server resources. The longer the session expires, the more storage resources the server may need to spend. Although the server usually does not cache messages for clients without limit. Taking [EMQX](https://www.emqx.io) as an example, the maximum number of messages that can be cached in each client session is 1000 by default, but considering the number of clients, this may still be an objective storage cost. If your server has limited resources, then you may need to be more careful with setting the session expiration time and the maximum cache of sessions. +For example, we need to correctly evaluate the impact of persistent sessions on server resources. The longer the session expires, the more storage resources the server may need to spend. Although the server usually does not cache messages for clients without limit. Taking [EMQX](https://github.com/emqx/emqx) as an example, the maximum number of messages that can be cached in each client session is 1000 by default, but considering the number of clients, this may still be an objective storage cost. If your server has limited resources, then you may need to be more careful with setting the session expiration time and the maximum cache of sessions. In addition, we also need to evaluate whether it is necessary for the client to continue processing messages arriving during these offline periods after being offline for a long time. Of course, setting a larger cache to save as many messages as possible, or setting a smaller cache to allow the client to only process messages that have arrived recently, mainly depends on your actual scenario. diff --git a/en/202310/navigating-urban-traffic-with-ekuiper.md b/en/202310/navigating-urban-traffic-with-ekuiper.md index 412f60b3..b45bf6b3 100644 --- a/en/202310/navigating-urban-traffic-with-ekuiper.md +++ b/en/202310/navigating-urban-traffic-with-ekuiper.md @@ -2,7 +2,7 @@ Real-time data is becoming a cornerstone in urban planning and traffic managemen ## **eKuiper: Real-Time Data Analysis at the Edge** -Our journey of personal traffic analysis starts with an open-source tool: [eKuiper](https://ekuiper.org/). Initiated by [EMQX](https://www.emqx.io/), this open-source marvel is not just lightweight and scalable but also boasts powerful edge computing capabilities. Its SQL-like syntax ensures that even those with a rudimentary understanding of data querying can harness its power. For traffic enthusiasts, eKuiper's real-time data processing provides a granular understanding of road conditions. +Our journey of personal traffic analysis starts with an open-source tool: [eKuiper](https://ekuiper.org/). Initiated by [EMQX](https://github.com/emqx/emqx), this open-source marvel is not just lightweight and scalable but also boasts powerful edge computing capabilities. Its SQL-like syntax ensures that even those with a rudimentary understanding of data querying can harness its power. For traffic enthusiasts, eKuiper's real-time data processing provides a granular understanding of road conditions. ## **Getting Started with eKuiper** diff --git a/en/202310/opc-ua-protocol.md b/en/202310/opc-ua-protocol.md index 51a95d27..1411ee91 100644 --- a/en/202310/opc-ua-protocol.md +++ b/en/202310/opc-ua-protocol.md @@ -194,7 +194,7 @@ Pub-Sub security is a bit more complex than that in client/server, and the speci [Neuron](https://neugates.io/) is a modern industrial IoT connectivity server that can connect to a wide range of industrial devices using standard or device-proprietary protocols, enabling the interconnection of [industrial IoT platforms](https://www.emqx.com/en/blog/iiot-platform-key-components-and-5-notable-solutions) with massive devices. As a lightweight industrial protocol gateway software, Neuron is designed to operate on various IoT edge hardware devices with limited resources. Its primary goal is to address the challenge of accessing data from data-centric automation equipment in a unified manner, thus offering essential support for smart manufacturing. -[EMQX](https://www.emqx.io/) is a distributed [open-source MQTT broker](https://www.emqx.com/en/blog/a-comprehensive-comparison-of-open-source-mqtt-brokers-in-2023). As the world's most scalable MQTT messaging server, EMQX provides efficient and reliable connectivity to a massive number of IoT devices, enabling high-performance, real-time movement and processing of messages and event streams, helping users rapidly build business-critical IoT platforms and applications. +[EMQX](https://github.com/emqx/emqx) is a distributed [open-source MQTT broker](https://www.emqx.com/en/blog/a-comprehensive-comparison-of-open-source-mqtt-brokers-in-2023). As the world's most scalable MQTT messaging server, EMQX provides efficient and reliable connectivity to a massive number of IoT devices, enabling high-performance, real-time movement and processing of messages and event streams, helping users rapidly build business-critical IoT platforms and applications. OPC UA data sources can be captured and aggregated by Neuron's southbound OPC UA driver, converted to the MQTT protocol, and transmitted to the EMQX MQTT Broker. The latter then distributes them to various distributed applications. diff --git a/en/202310/open-telemetry-the-basics-and-benefits-for-mqtt-and-iot-observability.md b/en/202310/open-telemetry-the-basics-and-benefits-for-mqtt-and-iot-observability.md index 9c8153f9..29d14f8d 100644 --- a/en/202310/open-telemetry-the-basics-and-benefits-for-mqtt-and-iot-observability.md +++ b/en/202310/open-telemetry-the-basics-and-benefits-for-mqtt-and-iot-observability.md @@ -100,7 +100,7 @@ Error and fault metrics are essential for understanding the reliability of your ## EMQX MQTT Platform: Supporting OpenTelemetry Integration -[EMQX](https://www.emqx.io/), a leader in the field of MQTT brokers, has integrated the robust capabilities of OpenTelemetry. EMQX 5.2 provides a direct channel to send metrics to the OpenTelemetry Collector, using the gRPC OTEL protocol. +[EMQX](https://github.com/emqx/emqx), a leader in the field of MQTT brokers, has integrated the robust capabilities of OpenTelemetry. EMQX 5.2 provides a direct channel to send metrics to the OpenTelemetry Collector, using the gRPC OTEL protocol. This integration not only optimizes data transmission but also ensures telemetry data can be effectively directed, processed, and adapted to diverse backends, from open-source platforms like Jaeger and Prometheus to specialized commercial solutions. diff --git a/en/202310/what-is-a-smart-factory-key-components-4-levels-of-evolution.md b/en/202310/what-is-a-smart-factory-key-components-4-levels-of-evolution.md index b6227fc8..ae18d253 100644 --- a/en/202310/what-is-a-smart-factory-key-components-4-levels-of-evolution.md +++ b/en/202310/what-is-a-smart-factory-key-components-4-levels-of-evolution.md @@ -140,7 +140,7 @@ This involves implementing security protocols, encrypting data, and regularly up EMQ provides [Neuron](https://www.emqx.com/en/products/neuronex), a lightweight connectivity server for industrial dataops and data-centric automation, tightly integrated with our industry-leading [MQTT broker](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison). Neuron provides several significant benefits for IIoT, simplifying connectivity, enhancing data integration, and enabling real-time communication and analytics. -If you are a managing an IIoT deployment, [EMQX](https://www.emqx.io/) and [Neuron](https://www.emqx.com/en/products/neuronex) can help with: +If you are a managing an IIoT deployment, [EMQX](https://github.com/emqx/emqx) and [Neuron](https://www.emqx.com/en/products/neuronex) can help with: 1. **IT Connectivity:** EMQX broker offers a wide range of data bridges, facilitating seamless integration with over 40 cloud services and enterprise systems. This enables instant access to data across diverse applications, reducing the cost and complexity of custom bridge development. EMQX supports integration with popular databases like [MySQL](https://www.emqx.com/en/blog/mqtt-to-mysql), [PostgreSQL](https://www.emqx.com/en/blog/build-an-iot-time-series-data-application-for-energy-storage-with-mqtt-and-timescale), [MongoDB](https://www.emqx.com/en/blog/mqtt-and-mongodb-crafting-seamless-synergy-for-iot-data-mangement), and more, as well as technologies like [Redis](https://www.emqx.com/en/blog/mqtt-and-redis), Oracle, SAP, and [Kafka](https://www.emqx.com/en/blog/mqtt-and-kafka). This rich set of connectors ensures efficient IT connectivity and data exchange within the IIoT ecosystem. 2. **OT Connectivity:** Neuron serves as a protocol gateway, providing a comprehensive set of industrial connectivity options essential for successful IIoT deployments. With support for over 30 industrial protocols such as [Modbus](https://www.emqx.com/en/blog/modbus-protocol-the-grandfather-of-iot-communication), Ethernet/IP, Profinet I/O, OPC-UA, IEC104, [BACnet](https://www.emqx.com/en/blog/bacnet-protocol-basic-concepts-structure-obejct-model-explained), and more, Neuron enables seamless communication with various devices and systems across the operational technology (OT) landscape. Whether it's PLCs, building automation systems, CNC machines, or robotics, Neuron offers a powerful range of drivers to ensure reliable OT connectivity and data acquisition. diff --git a/en/202311/knx-protocol.md b/en/202311/knx-protocol.md index 4fc86e4b..07954db8 100644 --- a/en/202311/knx-protocol.md +++ b/en/202311/knx-protocol.md @@ -105,7 +105,7 @@ Since version 2.1.0, Neuron provides the [KNX plugin](https://neugates.io/docs/e ### EMQX for Handling MQTT Messages -[EMQX](https://www.emqx.io/) is the world’s leading open-source distributed MQTT broker with high performance and scalability. It provides efficient and reliable connections for massive IoT devices, enabling high-performance real-time movement and processing of the message and event flow data, helping users quickly build IoT platforms and applications for critical business. +[EMQX](https://github.com/emqx/emqx) is the world’s leading open-source distributed MQTT broker with high performance and scalability. It provides efficient and reliable connections for massive IoT devices, enabling high-performance real-time movement and processing of the message and event flow data, helping users quickly build IoT platforms and applications for critical business. EMQX is the broker component in the bridging architecture, while Neuron collects data from KNX devices and transmits the data in MQTT messages to the broker. After receiving the MQTT messages from Neuron, EMQX will then forward the data or perform further processing. diff --git a/en/202311/running-mqtt-on-kubernetes.md b/en/202311/running-mqtt-on-kubernetes.md index dc253212..fffb902e 100644 --- a/en/202311/running-mqtt-on-kubernetes.md +++ b/en/202311/running-mqtt-on-kubernetes.md @@ -133,7 +133,7 @@ To deploy EMQX Open Source via the EMQX Operator. To learn more about the EQMX C ## EMQX: A Kubernetes-Ready MQTT Broker -[EMQX](https://www.emqx.io/) is one of the most popular MQTT brokers. It stands out as a remarkably well-suited MQTT broker for deployment within Kubernetes environments. This type of deployment offers seamless integration of EMQX’s robust messaging capabilities with Kubernetes' ability to handle rapidly changing workloads and efficiently manage containers. +[EMQX](https://github.com/emqx/emqx) is one of the most popular MQTT brokers. It stands out as a remarkably well-suited MQTT broker for deployment within Kubernetes environments. This type of deployment offers seamless integration of EMQX’s robust messaging capabilities with Kubernetes' ability to handle rapidly changing workloads and efficiently manage containers. ![MQTT Broker Cluster](https://assets.emqx.com/images/b39739558e71f83c6ecf70c0df22d918.png) diff --git a/en/202312/coap-protocol.md b/en/202312/coap-protocol.md index 9dbb56ff..775b5b3f 100644 --- a/en/202312/coap-protocol.md +++ b/en/202312/coap-protocol.md @@ -135,7 +135,7 @@ The following table summarizes the detailed comparison of the two protocols: CoAP supports communication between low-consumption, low-power devices on constrained networks. While CoAP works well in restricted networks, it falls short when devices need to communicate with external networks. In addition, CoAP lacks support for resource processing centers because it was designed with the M2M network model in mind (the CoAP-based LwM2M protocol introduces concepts such as resource registration and resource services). -This problem can be solved using [EMQX](https://www.emqx.io/), the leading open source MQTT message broker. For CoAP devices that need to communicate with external networks, using EMQX as a broker makes it easy to: +This problem can be solved using [EMQX](https://github.com/emqx/emqx), the leading open source MQTT message broker. For CoAP devices that need to communicate with external networks, using EMQX as a broker makes it easy to: - Authenticate devices and reject data from untrustworthy devices. - Manage resource permissions, including specifying different resource read/write permissions for different devices. diff --git a/en/202312/running-mqtt-broker-on-docker.md b/en/202312/running-mqtt-broker-on-docker.md index 25cf1084..b646e15e 100644 --- a/en/202312/running-mqtt-broker-on-docker.md +++ b/en/202312/running-mqtt-broker-on-docker.md @@ -4,7 +4,7 @@ This combination provides a scalable and reliable solution to handle data streams in real-time, particularly in IoT applications. The MQTT broker receives messages from publishers (devices or applications that produce data) and dispatches them to subscribers (devices or applications that consume data). By running the broker on Docker, you can make it easier to deploy and scale your MQTT broker. -We’ll show how to deploy MQTT on Docker with [EMQX](https://www.emqx.io/), a popular, open source MQTT broker. EMQX provides powerful capabilities not available in other open source brokers, such as clustering, persistence, and support for very large scale deployments. +We’ll show how to deploy MQTT on Docker with [EMQX](https://github.com/emqx/emqx), a popular, open source MQTT broker. EMQX provides powerful capabilities not available in other open source brokers, such as clustering, persistence, and support for very large scale deployments. ## Why Should You Run an MQTT Broker on Docker? diff --git a/en/202401/mqtt-with-zigbee-a-practical-guide.md b/en/202401/mqtt-with-zigbee-a-practical-guide.md index cc51611a..d0dbbb93 100644 --- a/en/202401/mqtt-with-zigbee-a-practical-guide.md +++ b/en/202401/mqtt-with-zigbee-a-practical-guide.md @@ -111,7 +111,7 @@ Zigbee2MQTT:info 2019-11-09T12:19:56: Successfully interviewed '0x00158d0001dc12 Zigbee has a wide range of applications in fields such as smart home and industrial manufacturing. Zigbee2MQTT allows you to manage Zigbee devices uniformly with the help of an [MQTT broker](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison), and also makes it possible for Zigbee devices to work in cooperation with MQTT devices. In order for Zigbee devices and MQTT devices to communicate stably and efficiently, a reliable MQTT broker is necessary. -[EMQX](https://www.emqx.io/), as a high-performance, scalable open-source MQTT broker, can easily handle a large number of concurrent connections and message throughput, and ensure millisecond-level message latency. Even on machines with limited resources like Raspberry Pi, you can easily install and run EMQX. In addition, EMQX provides a wealth of APIs and management interfaces, which makes it easy for you to monitor system status, manage clients and topics, and even dynamically adjust configurations to cope with constantly changing business needs. +[EMQX](https://github.com/emqx/emqx), as a high-performance, scalable open-source MQTT broker, can easily handle a large number of concurrent connections and message throughput, and ensure millisecond-level message latency. Even on machines with limited resources like Raspberry Pi, you can easily install and run EMQX. In addition, EMQX provides a wealth of APIs and management interfaces, which makes it easy for you to monitor system status, manage clients and topics, and even dynamically adjust configurations to cope with constantly changing business needs. These features make EMQX an ideal choice for the Zigbee2MQTT project. Visit our [official website](https://www.emqx.com/en) to learn more. diff --git a/en/202402/mqtt-sparkplug-bridging-it-and-ot-in-industry-4-0.md b/en/202402/mqtt-sparkplug-bridging-it-and-ot-in-industry-4-0.md index e74fa8f6..87921678 100644 --- a/en/202402/mqtt-sparkplug-bridging-it-and-ot-in-industry-4-0.md +++ b/en/202402/mqtt-sparkplug-bridging-it-and-ot-in-industry-4-0.md @@ -85,7 +85,7 @@ The use of a unified namespace in Sparkplug simplifies the process of managing a To implement an MQTT Sparkplug solution, we need two components: an MQTT server and an edge node. -An [MQTT server](https://www.emqx.io/) is used as the central broker for handling the communication between devices and applications in an IIoT environment. The MQTT server is responsible for receiving messages from devices, forwarding them to the appropriate subscribers, and storing messages for later retrieval if necessary. +An [MQTT server](https://github.com/emqx/emqx) is used as the central broker for handling the communication between devices and applications in an IIoT environment. The MQTT server is responsible for receiving messages from devices, forwarding them to the appropriate subscribers, and storing messages for later retrieval if necessary. An edge node is a device or gateway that acts as an intermediary between devices and the [MQTT broker](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison). It can handle local data processing and aggregation, as well as buffering and forwarding data to the MQTT broker. Edge nodes are typically used in IIoT environments where numerous devices generate large amounts of data and where network bandwidth is limited. diff --git a/en/202402/mqtt-sparkplug-in-action-a-step-by-step-tutorial.md b/en/202402/mqtt-sparkplug-in-action-a-step-by-step-tutorial.md index cd5ff5a6..a30e6397 100644 --- a/en/202402/mqtt-sparkplug-in-action-a-step-by-step-tutorial.md +++ b/en/202402/mqtt-sparkplug-in-action-a-step-by-step-tutorial.md @@ -18,7 +18,7 @@ In the context of MQTT Sparkplug, edge nodes are responsible for implementing th In this blog, we will demonstrate how to get started with MQTT Sparkplug using EMQX and Neuron. -[EMQX](https://www.emqx.io/) is a popular MQTT broker that supports the Sparkplug protocol, while Neuron is an [industrial IoT platform](https://www.emqx.com/en/blog/iiot-platform-key-components-and-5-notable-solutions) that can be used to collect data from industrial devices and generate Sparkplug messages for applications. +[EMQX](https://github.com/emqx/emqx) is a popular MQTT broker that supports the Sparkplug protocol, while Neuron is an [industrial IoT platform](https://www.emqx.com/en/blog/iiot-platform-key-components-and-5-notable-solutions) that can be used to collect data from industrial devices and generate Sparkplug messages for applications. [Neuron](https://neugates.io/) can collect the data from the devices and publish Sparkplug messages to the EMQX broker based on the data by reporting changes. EMQX will forward the messages to the application that subscribes to the relevant Sparkplug topic. However, EMQX is able to decode the Sparkplug messages through the rules engine. The messages are then used for data platforms, persistent storage for historical, and so on. @@ -26,7 +26,7 @@ In this blog, we will demonstrate how to get started with MQTT Sparkplug using E ### Install EMQX -Download and install the EMQX MQTT broker on your server or machine. EMQX provides a community edition that can be downloaded for free from their website. Visit the website [http://www.emqx.io/](https://docs.emqx.com/en/emqx/latest/deploy/install.html) and follow the documentation. +Download and install the EMQX MQTT broker on your server or machine. EMQX provides a community edition that can be downloaded for free from their website. Visit the website [https://docs.emqx.com/en/emqx/latest/deploy/install.html](https://docs.emqx.com/en/emqx/latest/deploy/install.html) and follow the documentation. ### Create Schema Registry in EMQX diff --git a/en/202403/mqtt-and-kafka.md b/en/202403/mqtt-and-kafka.md index 74904900..83e059ea 100644 --- a/en/202403/mqtt-and-kafka.md +++ b/en/202403/mqtt-and-kafka.md @@ -36,7 +36,7 @@ When integrating MQTT and Kafka in an IoT platform, several viable solutions are ### EMQX Kafka Data Integration -[EMQX](https://www.emqx.io/) is a popular [MQTT broker](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison) that offers seamless integration with Kafka through its Kafka Data Integration feature. As a bridge between MQTT and Kafka, EMQX enables smooth communication between the two protocols. +[EMQX](https://github.com/emqx/emqx) is a popular [MQTT broker](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison) that offers seamless integration with Kafka through its Kafka Data Integration feature. As a bridge between MQTT and Kafka, EMQX enables smooth communication between the two protocols. This integration allows the creation of data bridges to Kafka in two roles: producer (sending messages to Kafka) and consumer (receiving messages from Kafka). EMQX allows users to establish data bridges in either of these roles. With its bi-directional data transmission capability, EMQX provides flexibility in architecture design. Additionally, it offers low latency and high throughput, ensuring efficient and reliable data-bridging operations. diff --git a/en/202404/emqx-open-source-vs-enterprise.md b/en/202404/emqx-open-source-vs-enterprise.md index 0b73dfc2..187fee5d 100644 --- a/en/202404/emqx-open-source-vs-enterprise.md +++ b/en/202404/emqx-open-source-vs-enterprise.md @@ -8,7 +8,7 @@ EMQX is a scalable, distributed MQTT messaging platform that supports unlimited - [EMQX Dedicated](https://www.emqx.com/en/cloud/dedicated): A single-tenant MQTT service with capacity-based pricing, offering advanced settings and expert support. - [EMQX BYOC](https://www.emqx.com/en/cloud/byoc): Allows hosting EMQX clusters on your own cloud, fully managed by the EMQ team with advanced options. - [EMQX Enterprise](https://www.emqx.com/en/products/emqx): A self-managed EMQX Cluster, deployable anywhere to handle enterprise-grade workloads. -- [EMQX Open Source](https://www.emqx.io/): A community-supported open-source MQTT broker. +- [EMQX Open Source](https://github.com/emqx/emqx): A community-supported open-source MQTT broker. This blog explores the distinctions between EMQX Enterprise and Open Source editions, highlighting their respective capabilities and offerings to help you identify the most suitable option for your IoT business. diff --git a/en/202404/free-mqtt-broker.md b/en/202404/free-mqtt-broker.md index ec3e9ffa..1d38723e 100644 --- a/en/202404/free-mqtt-broker.md +++ b/en/202404/free-mqtt-broker.md @@ -14,7 +14,7 @@ This blog will introduce the common free MQTT brokers available and how to choos **Popular Open Source MQTT Broker:** -- EMQX: [EMQX](https://www.emqx.io/) is one of the most popular open source MQTT brokers and has 11.5k stars on GitHub. It is the world's most scalable MQTT broker that supports masterless clustering for high availability and horizontal scalability. EMQX is widely used for business-critical applications in various industries, such as IoT, [industrial IoT](https://www.emqx.com/en/use-cases/industrial-iot), [connected cars](https://www.emqx.com/en/blog/connected-cars-and-automotive-connectivity-all-you-need-to-know), [manufacturing](https://docs.emqx.com/en/enterprise/latest/), and telecommunications. +- EMQX: [EMQX](https://github.com/emqx/emqx) is one of the most popular open source MQTT brokers and has 11.5k stars on GitHub. It is the world's most scalable MQTT broker that supports masterless clustering for high availability and horizontal scalability. EMQX is widely used for business-critical applications in various industries, such as IoT, [industrial IoT](https://www.emqx.com/en/use-cases/industrial-iot), [connected cars](https://www.emqx.com/en/blog/connected-cars-and-automotive-connectivity-all-you-need-to-know), [manufacturing](https://docs.emqx.com/en/enterprise/latest/), and telecommunications. - Mosquitto: [Mosquitto](https://www.emqx.com/en/blog/mosquitto-mqtt-broker-pros-cons-tutorial-and-modern-alternatives) is known for its lightweight footprint, making it suitable for resource-constrained environments commonly found in IoT deployments. It supports the [MQTT protocol](https://www.emqx.com/en/blog/the-easiest-guide-to-getting-started-with-mqtt) versions 3.1, 3.1.1, and 5.0, providing flexibility and compatibility with a wide range of MQTT clients and devices. - NanoMQ: [NanoMQ](https://nanomq.io/) is a lightweight and fast MQTT messaging broker designed for edge computing scenarios in IoT. It is lightweight and high-performance, making it suitable for various edge computing platforms. diff --git a/ja/202305/how-to-use-mqtt-in-nodejs.md b/ja/202305/how-to-use-mqtt-in-nodejs.md index 7cd1e6cd..301ef298 100644 --- a/ja/202305/how-to-use-mqtt-in-nodejs.md +++ b/ja/202305/how-to-use-mqtt-in-nodejs.md @@ -4,7 +4,7 @@ Node.jsは、イベント駆動型のアーキテクチャとリアルタイムのデータハンドリングにより、IoTで広く利用されています。デバイス、サーバ、APIを簡単に接続することができます。Node.jsとMQTTを組み合わせることで、開発者は、デバイスとリアルタイムで通信し、情報を交換し、複雑なデータ分析を行う、スケーラブルで安全なIoTアプリケーションを構築できます。 -この記事では、Node.jsプロジェクトでMQTTを使用して、クライアントと[MQTTブローカー](https://www.emqx.io/)間のシームレスな通信を実現するための包括的なガイドを提供します。接続の確立、トピックのサブスクライブとアンサブスクライブ、メッセージの公開、およびリアルタイムでのメッセージの受信方法について学びます。このガイドでは、MQTTを活用してスケーラブルで効率的なIoTアプリケーションを構築するためのスキルを身につけることができます。 +この記事では、Node.jsプロジェクトでMQTTを使用して、クライアントと[MQTTブローカー](https://github.com/emqx/emqx)間のシームレスな通信を実現するための包括的なガイドを提供します。接続の確立、トピックのサブスクライブとアンサブスクライブ、メッセージの公開、およびリアルタイムでのメッセージの受信方法について学びます。このガイドでは、MQTTを活用してスケーラブルで効率的なIoTアプリケーションを構築するためのスキルを身につけることができます。 ## Node.js MQTTプロジェクト準備編 @@ -48,7 +48,7 @@ MQTT.jsのインストールには、NPMやYarnを使用します。 - **プライベート展開** - [EMQX](https://www.emqx.io/)は、IoT、IIoT、コネクテッドカー向けの最もスケーラブルなオープンソースのMQTTブローカーです。以下のDockerコマンドを実行することでEMQXをインストールすることができます。 + [EMQX](https://github.com/emqx/emqx)は、IoT、IIoT、コネクテッドカー向けの最もスケーラブルなオープンソースのMQTTブローカーです。以下のDockerコマンドを実行することでEMQXをインストールすることができます。 ``` docker run -d --name emqx -p 1883:1883 -p 8083:8083 -p 8084:8084 -p 8883:8883 -p 18083:18083 emqx/emqx diff --git a/ja/202305/top-3-open-source-mqtt-brokers-for-industrial-iot-in-2023.md b/ja/202305/top-3-open-source-mqtt-brokers-for-industrial-iot-in-2023.md index ca51ef4a..bd02a96a 100644 --- a/ja/202305/top-3-open-source-mqtt-brokers-for-industrial-iot-in-2023.md +++ b/ja/202305/top-3-open-source-mqtt-brokers-for-industrial-iot-in-2023.md @@ -20,7 +20,7 @@ GitHubでホストされている3つのプロジェクトの概要は以下の | | **EMQX** | **Mosquitto** | **NanoMQ** | | :---------------------------------- | :------------------------------------------ | :------------------------------------------------------- | :---------------------------------------------- | -| **Official Website** | [EMQX](https://www.emqx.io/) | [Eclipse Mosquitto](https://mosquitto.org/) | [NanoMQ](https://nanomq.io/) | +| **Official Website** | [EMQX](https://github.com/emqx/emqx) | [Eclipse Mosquitto](https://mosquitto.org/) | [NanoMQ](https://nanomq.io/) | | **GitHub Project** | [EMQX GitHub](https://github.com/emqx/emqx) | [Mosquitto GitHub](https://github.com/eclipse/mosquitto) | [NanoMQ GitHub](https://github.com/nanomq/nanomq) | | **Project Created** | 2012 | 2009 | 2020 | | **License** | Apache License 2.0 | EPL/EDL License | MIT License | @@ -35,7 +35,7 @@ GitHubでホストされている3つのプロジェクトの概要は以下の ## 1. EMQX -[EMQX](https://www.emqx.io/)は、企業のIIoT展開のための高度にスケーラブルな分散型MQTTブローカーです。MQTT 5.0、MQTT-SN、SSL/TLS暗号化、[MQTT over QUIC](https://www.emqx.com/en/blog/mqtt-over-quic)を幅広くサポートしています。さらに、マスターレスクラスタリングにより、高可用性と水平スケーラビリティを実現します。 +[EMQX](https://github.com/emqx/emqx)は、企業のIIoT展開のための高度にスケーラブルな分散型MQTTブローカーです。MQTT 5.0、MQTT-SN、SSL/TLS暗号化、[MQTT over QUIC](https://www.emqx.com/en/blog/mqtt-over-quic)を幅広くサポートしています。さらに、マスターレスクラスタリングにより、高可用性と水平スケーラビリティを実現します。 EMQXはGitHubで11.5kのスターを獲得しており、[最も人気のあるMQTTブローカー](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison)の1つとしての地位を確立しています。EMQXプロジェクトは2012年に開始され、Apacheバージョン2.0の下でライセンスされています。EMQXは、大規模なスケーラブルソフトリアルタイムシステムを構築するためのプログラミング言語であるErlang/OTPで書かれています。 @@ -147,7 +147,7 @@ Unified Namespace（UNS）は、産業用IoTおよびインダストリー4.0向 ## 結論 -これまでの紹介と比較から、各MQTTブローカーは異なる展開シナリオに対して明確な強みを提供することができます。 [EMQX](https://www.emqx.io/) は、エンタープライズ向けの機能で拡張性が高く、クラウド展開に適しています。 [Mosquitto](https://mosquitto.org/)と[NanoMQ](https://nanomq.io/)は、高速かつ軽量で、産業用ゲートウェイに最適です。 +これまでの紹介と比較から、各MQTTブローカーは異なる展開シナリオに対して明確な強みを提供することができます。 [EMQX](https://github.com/emqx/emqx) は、エンタープライズ向けの機能で拡張性が高く、クラウド展開に適しています。 [Mosquitto](https://mosquitto.org/)と[NanoMQ](https://nanomq.io/)は、高速かつ軽量で、産業用ゲートウェイに最適です。 これら3つのMQTTブローカーは、産業用IoTアプリケーションにおいて重要な役割を果たし、UNSアーキテクチャの実装を先導し、ITとOTドメインの融合を促進する。具体的なIIoTプロジェクトを検討する際には、要件に応じてこれらのMQTTブローカーのうち1つまたは2つを選択することができます。それぞれの強みを生かすことで、MQTTブローカーが連携し、それぞれの能力を相乗的に発揮する、まとまったシステムを構築することができます。 diff --git a/ja/202306/can-bus-how-it-works-pros-and-cons.md b/ja/202306/can-bus-how-it-works-pros-and-cons.md index 6bd3c8b3..15c62c77 100644 --- a/ja/202306/can-bus-how-it-works-pros-and-cons.md +++ b/ja/202306/can-bus-how-it-works-pros-and-cons.md @@ -6,7 +6,7 @@ CAN Busは、1980年代にBosch社によって自動車用に設計されたも CAN Busデータは、接続されたデバイスのパフォーマンスとステータスに関する貴重な洞察を提供することができます。しかし、CAN Busデータの収集と処理は、高いデータレート、低い帯域幅、および変化するネットワーク条件のために困難である可能性があります。 -これらの課題を克服するための一つの解決策として、[MQTT](https://www.emqx.com/ja/blog/the-easiest-guide-to-getting-started-with-mqtt)を使用することが考えられ、弱いネットワーク条件でも自動車からクラウドへのタイムリーなデータ伝送を可能にします。EMQXは[オープンソースのMQTTブローカー](https://www.emqx.io/)で、CAN Busデータを収集するための信頼性と拡張性の高いMQTTインフラストラクチャを構築するのに役立ちます。 +これらの課題を克服するための一つの解決策として、[MQTT](https://www.emqx.com/ja/blog/the-easiest-guide-to-getting-started-with-mqtt)を使用することが考えられ、弱いネットワーク条件でも自動車からクラウドへのタイムリーなデータ伝送を可能にします。EMQXは[オープンソースのMQTTブローカー](https://github.com/emqx/emqx)で、CAN Busデータを収集するための信頼性と拡張性の高いMQTTインフラストラクチャを構築するのに役立ちます。 ![CAN Bus](https://assets.emqx.com/images/e8c8c72601898e841855a8efa306d63e.png) @@ -184,7 +184,7 @@ SELECT signal1, signal2 FROM canStream WHERE signal1 > 100 ## MQTTを使ったCAN Busのデータ収集 -CAN Busのデータ収集に[EMQX](https://www.emqx.io/)のようなMQTTブローカーを使用すると、以下のようなメリットがあります： +CAN Busのデータ収集に[EMQX](https://github.com/emqx/emqx)のようなMQTTブローカーを使用すると、以下のようなメリットがあります： - ネットワークのオーバーヘッドを削減：MQTTは、バイナリフォーマットと最小限のヘッダーを使用してメッセージをエンコードするため、ネットワーク帯域幅の消費を抑え、データ伝送効率を向上させることができます。 - スケーラビリティの向上：MQTTは、1つのブローカーで数千の同時接続と数百万メッセージ/秒をサポートすることができます。これにより、性能や信頼性を損なうことなく、複数のCAN Busデバイスから大規模なデータ収集を行うことができます。 diff --git a/ja/202306/emqx-vs-mosquitto-2023-mqtt-broker-comparison.md b/ja/202306/emqx-vs-mosquitto-2023-mqtt-broker-comparison.md index adb38cb4..375838ff 100644 --- a/ja/202306/emqx-vs-mosquitto-2023-mqtt-broker-comparison.md +++ b/ja/202306/emqx-vs-mosquitto-2023-mqtt-broker-comparison.md @@ -2,7 +2,7 @@ MQTT（Message Queuing Telemetry Transport）は、IoT（Internet of Things）のデファクトスタンダードなメッセージングプロトコルである。IoTの発展に伴い、[MQTTブローカー](https://www.emqx.com/en/blog/the-ultimate-guide-to-mqtt-broker-comparison)はIoT機器の接続や、接続された機器とクラウドサービス間のデータ移動に不可欠になっています。 -[EMQX](https://www.emqx.io/)と[Mosquitto](https://mosquitto.org/)は、最も人気のあるオープンソースのMQTTブローカーの2つです。EMQXは、拡張性の高い分散型MQTTブローカーで、クラスタリングをサポートしています。Mosquittoは、フットプリントが小さく、シングルスレッド・アーキテクチャの軽量なMQTTブローカーです。 +[EMQX](https://github.com/emqx/emqx)と[Mosquitto](https://mosquitto.org/)は、最も人気のあるオープンソースのMQTTブローカーの2つです。EMQXは、拡張性の高い分散型MQTTブローカーで、クラスタリングをサポートしています。Mosquittoは、フットプリントが小さく、シングルスレッド・アーキテクチャの軽量なMQTTブローカーです。 このブログ記事では、2023年の2つのブローカーを詳細に比較します。 @@ -247,7 +247,7 @@ EMQXは、高可用性と水平方向のスケーラビリティをサポート - [Eclipse Mosquitto](https://mosquitto.org/) - [Eclipse Mosquitto Documentation](https://mosquitto.org/documentation/) -- [EMQX: The World's #1 Open Source Distributed MQTT Broker](https://www.emqx.io/) +- [EMQX: The World's #1 Open Source Distributed MQTT Broker](https://github.com/emqx/emqx) - [EMQX 5.0 Documentation](https://docs.emqx.com/en/emqx/v5.0/) - [EMQX Enterprise Documentation](https://docs.emqx.com/en/enterprise/v5.0/) - [EMQX Operator Documentation](https://docs.emqx.com/en/emqx-operator/latest/) diff --git a/ja/202306/esp32-connects-to-the-free-public-mqtt-broker.md b/ja/202306/esp32-connects-to-the-free-public-mqtt-broker.md index 075846c3..60e0b73e 100644 --- a/ja/202306/esp32-connects-to-the-free-public-mqtt-broker.md +++ b/ja/202306/esp32-connects-to-the-free-public-mqtt-broker.md @@ -18,7 +18,7 @@ ESP32でMQTTを使うことには以下のような利点があります： - **プライベート展開** - [EMQX](https://www.emqx.io/)は、IoT、IIoT、コネクテッドカー向けの最もスケーラブルなオープンソースのMQTTブローカーです。以下のDockerコマンドを実行することでEMQXをインストールすることができます。 + [EMQX](https://github.com/emqx/emqx)は、IoT、IIoT、コネクテッドカー向けの最もスケーラブルなオープンソースのMQTTブローカーです。以下のDockerコマンドを実行することでEMQXをインストールすることができます。 ``` docker run -d --name emqx -p 1883:1883 -p 8083:8083 -p 8084:8084 -p 8883:8883 -p 18083:18083 emqx/emqx diff --git a/ja/202306/how-to-use-mqtt-in-python.md b/ja/202306/how-to-use-mqtt-in-python.md index 80e2b39b..2687e002 100644 --- a/ja/202306/how-to-use-mqtt-in-python.md +++ b/ja/202306/how-to-use-mqtt-in-python.md @@ -4,7 +4,7 @@ Pythonは、その汎用性、使いやすさ、膨大なライブラリから、IoTで広く利用されています。大量のデータを扱うことができるため、スマートホームオートメーション、環境モニタリング、産業制御などに最適です。また、Pythonはマイクロコントローラと互換性があるため、IoTデバイスの開発にも有効なツールとなっています。 -本記事では、主にPythonプロジェクトにおいて、paho-mqttクライアントを使用し、[MQTTクライアント](https://www.emqx.com/ja/blog/mqtt-client-tools)と[MQTTブローカー](https://www.emqx.io/)間の接続、購読、メッセージングなどの機能を実装する方法について紹介します。 +本記事では、主にPythonプロジェクトにおいて、paho-mqttクライアントを使用し、[MQTTクライアント](https://www.emqx.com/ja/blog/mqtt-client-tools)と[MQTTブローカー](https://github.com/emqx/emqx)間の接続、購読、メッセージングなどの機能を実装する方法について紹介します。 ## Paho MQTT Python Clientを選択する理由は？ @@ -46,7 +46,7 @@ pip3 install paho-mqtt - **プライベート展開** - [EMQX](https://www.emqx.io/)は、IoT、IIoT、コネクテッドカー向けの最もスケーラブルなオープンソースのMQTTブローカーです。以下のDockerコマンドを実行することでEMQXをインストールすることができます。 + [EMQX](https://github.com/emqx/emqx)は、IoT、IIoT、コネクテッドカー向けの最もスケーラブルなオープンソースのMQTTブローカーです。以下のDockerコマンドを実行することでEMQXをインストールすることができます。 ``` docker run -d --name emqx -p 1883:1883 -p 8083:8083 -p 8084:8084 -p 8883:8883 -p 18083:18083 emqx/emqx diff --git a/ja/202306/mqtt-client-tools.md b/ja/202306/mqtt-client-tools.md index 5aacdcd0..5377de08 100644 --- a/ja/202306/mqtt-client-tools.md +++ b/ja/202306/mqtt-client-tools.md @@ -20,7 +20,7 @@ ## 無料公開のMQTTブローカー -MQTTクライアント・デスクトップ・ツールに飛び込む前に、通信とテストを行うための[MQTTブローカー](https://www.emqx.io/)が必要です。ここでは、 `broker.emqx.io` で利用できる無料のパブリックMQTTブローカーを選択します。 +MQTTクライアント・デスクトップ・ツールに飛び込む前に、通信とテストを行うための[MQTTブローカー](https://github.com/emqx/emqx)が必要です。ここでは、 `broker.emqx.io` で利用できる無料のパブリックMQTTブローカーを選択します。 > ***MQTTブローカー情報*** > diff --git a/ja/202306/mqtt-js-tutorial.md b/ja/202306/mqtt-js-tutorial.md index 4ce35973..bdd6bf0e 100644 --- a/ja/202306/mqtt-js-tutorial.md +++ b/ja/202306/mqtt-js-tutorial.md @@ -54,7 +54,7 @@ npm install mqtt -g - **プライベート展開** - [EMQX](https://www.emqx.io/)は、IoT、IIoT、コネクテッドビークルのための最もスケーラブルなオープンソースのMQTTブローカーです。EMQXをインストールするには、以下のDockerコマンドを実行します： + [EMQX](https://github.com/emqx/emqx)は、IoT、IIoT、コネクテッドビークルのための最もスケーラブルなオープンソースのMQTTブローカーです。EMQXをインストールするには、以下のDockerコマンドを実行します： ``` docker run -d --name emqx -p 1883:1883 -p 8083:8083 -p 8084:8084 -p 8883:8883 -p 18083:18083 emqx/emqx diff --git a/ja/202306/quic-protocol-the-features-use-cases-and-impact-for-iot-iov.md b/ja/202306/quic-protocol-the-features-use-cases-and-impact-for-iot-iov.md index 50fabd2f..aa79a337 100644 --- a/ja/202306/quic-protocol-the-features-use-cases-and-impact-for-iot-iov.md +++ b/ja/202306/quic-protocol-the-features-use-cases-and-impact-for-iot-iov.md @@ -95,7 +95,7 @@ MQTT over QUICのInternet of Vehiclesにおける使用例として、以下の ## EMQX: MQTTブローカーとして初めてMQTT Over QUICを実装し、技術を革新します -[EMQX](https://www.emqx.io/)は、高性能なリアルタイムメッセージ処理エンジンを搭載した、先進な[オープンソースのMQTTブローカー](https://www.emqx.com/en/blog/a-comprehensive-comparison-of-open-source-mqtt-brokers-in-2023)で、大規模なIoTデバイス向けのイベントストリーミングを強力にサポートします。バージョン5.0以降、EMQXはMQTTブローカーとして初めてMQTT over QUICをサポートし、現代の複雑なネットワーク上でMQTTメッセージをより効率的かつ安全に伝送する方法を提供し、特定のシナリオでMQTTのパフォーマンスを向上させました。 +[EMQX](https://github.com/emqx/emqx)は、高性能なリアルタイムメッセージ処理エンジンを搭載した、先進な[オープンソースのMQTTブローカー](https://www.emqx.com/en/blog/a-comprehensive-comparison-of-open-source-mqtt-brokers-in-2023)で、大規模なIoTデバイス向けのイベントストリーミングを強力にサポートします。バージョン5.0以降、EMQXはMQTTブローカーとして初めてMQTT over QUICをサポートし、現代の複雑なネットワーク上でMQTTメッセージをより効率的かつ安全に伝送する方法を提供し、特定のシナリオでMQTTのパフォーマンスを向上させました。 現在のEMQXサポートの実装では、トランスポート層をQUICストリームに置き換え、クライアントが接続を開始し双方向のストリームを作成します。EMQXは2つの動作モードをサポートしています： diff --git a/ja/202306/the-easiest-guide-to-getting-started-with-mqtt.md b/ja/202306/the-easiest-guide-to-getting-started-with-mqtt.md index 9d2678dd..20765260 100644 --- a/ja/202306/the-easiest-guide-to-getting-started-with-mqtt.md +++ b/ja/202306/the-easiest-guide-to-getting-started-with-mqtt.md @@ -87,7 +87,7 @@ MQTTの基本的な構成要素を理解したところで、一般的なワー - **プライベート展開** - [EMQX](https://www.emqx.io/)は、IoT、IIoT、コネクテッドカー向けの最もスケーラブルなオープンソースのMQTTブローカーです。以下のDockerコマンドを実行することでEMQXをインストールすることができます。 + [EMQX](https://github.com/emqx/emqx)は、IoT、IIoT、コネクテッドカー向けの最もスケーラブルなオープンソースのMQTTブローカーです。以下のDockerコマンドを実行することでEMQXをインストールすることができます。 ``` docker run -d --name emqx -p 1883:1883 -p 8083:8083 -p 8084:8084 -p 8883:8883 -p 18083:18083 emqx/emqx diff --git a/ja/202307/connect-to-mqtt-broker-with-websocket.md b/ja/202307/connect-to-mqtt-broker-with-websocket.md index 2aee5fad..e7621a0f 100644 --- a/ja/202307/connect-to-mqtt-broker-with-websocket.md +++ b/ja/202307/connect-to-mqtt-broker-with-websocket.md @@ -32,7 +32,7 @@ MQTT over WebSocketは、IoTデバイスへのアクセスを民主化し、ウ - **プライベート展開** - [EMQX](https://www.emqx.io/)は、IoT、IIoT、コネクテッドカー向けの最もスケーラブルなオープンソースのMQTTブローカーです。以下のDockerコマンドを実行することでEMQXをインストールすることができます。 + [EMQX](https://github.com/emqx/emqx)は、IoT、IIoT、コネクテッドカー向けの最もスケーラブルなオープンソースのMQTTブローカーです。以下のDockerコマンドを実行することでEMQXをインストールすることができます。 ``` docker run -d --name emqx -p 1883:1883 -p 8083:8083 -p 8084:8084 -p 8883:888 -p 18083:18083 emqx/emqx @@ -275,7 +275,7 @@ WebSocketは、単一のTCPコネクション上で持続的な全二重通信 ### EMQXに接続する際にパスを入力する必要があるのはなぜですか？ -WebSocket を使用して EMQX に接続する場合は、パスを入力する必要があります。これは、[EMQX](https://www.emqx.io/) が MQTT-WebSocket の統一パス仕様に従っているためです。この仕様では、MQTT over WebSocket トラフィックを識別および区別するために、WebSocket 接続で特定のパスを指定する必要があります。このパスは、MQTT over WebSocket トラフィックを MQTT Broker にルーティングして処理します。 +WebSocket を使用して EMQX に接続する場合は、パスを入力する必要があります。これは、[EMQX](https://github.com/emqx/emqx) が MQTT-WebSocket の統一パス仕様に従っているためです。この仕様では、MQTT over WebSocket トラフィックを識別および区別するために、WebSocket 接続で特定のパスを指定する必要があります。このパスは、MQTT over WebSocket トラフィックを MQTT Broker にルーティングして処理します。 EMQX では、MQTT over WebSocket のデフォルト・パスは `/mqtt` です。これは仕様に従って設定されています。したがって、EMQX に接続する場合は、接続が MQTT ブローカーに正しくルーティングされるように、このパスを WebSocket アドレスに含める必要があります。 diff --git a/ja/202307/mqtt-sparkplug-solution-for-industrial-iot-using-emqx-and-neuron.md b/ja/202307/mqtt-sparkplug-solution-for-industrial-iot-using-emqx-and-neuron.md index 9e0b4d8b..79094aca 100644 --- a/ja/202307/mqtt-sparkplug-solution-for-industrial-iot-using-emqx-and-neuron.md +++ b/ja/202307/mqtt-sparkplug-solution-for-industrial-iot-using-emqx-and-neuron.md @@ -2,11 +2,11 @@ Sparkplugは、産業オートメーションとIoTアプリケーションに特化したMQTTベースの通信プロトコルです。Sparkplugソリューションを実装するためには、[MQTTブローカー](https://www.emqx.com/ja/blog/the-ultimate-guide-to-mqtt-broker-comparison)とエッジノードという2つの重要な要素が必要です。 -この記事では、オープンソースの分散MQTTブローカーである[EMQX](https://www.emqx.io/)と、エッジIIoT接続サーバーである[Neuron](https://neugates.io/)を使用して、Sparkplugソリューションを構築するためのスケーラブルで堅牢なプラットフォームを提供します。Sparkplugソリューションのアーキテクチャと、EMQXとNeuronが果たす役割について詳しく掘り下げます。 +この記事では、オープンソースの分散MQTTブローカーである[EMQX](https://github.com/emqx/emqx)と、エッジIIoT接続サーバーである[Neuron](https://neugates.io/)を使用して、Sparkplugソリューションを構築するためのスケーラブルで堅牢なプラットフォームを提供します。Sparkplugソリューションのアーキテクチャと、EMQXとNeuronが果たす役割について詳しく掘り下げます。 ## EMQXの役割 -[EMQX](https://www.emqx.io/) を使用して、Sparkplug 仕様に準拠した [MQTT トピック](https://www.emqx.com/en/blog/advanced-features-of-mqtt-topics)名前空間を作成します。Sparkplug ネームスペースは、デバイスがパブリッシュおよびサブスクライブする MQTT メッセージの構造とコンテンツを定義します。EMQX は、Sparkplug ネームスペースに送受信されるすべてのメッセージが適切にフォーマットされ、Sparkplug 仕様に準拠していることを保証します。 +[EMQX](https://github.com/emqx/emqx) を使用して、Sparkplug 仕様に準拠した [MQTT トピック](https://www.emqx.com/en/blog/advanced-features-of-mqtt-topics)名前空間を作成します。Sparkplug ネームスペースは、デバイスがパブリッシュおよびサブスクライブする MQTT メッセージの構造とコンテンツを定義します。EMQX は、Sparkplug ネームスペースに送受信されるすべてのメッセージが適切にフォーマットされ、Sparkplug 仕様に準拠していることを保証します。 > *EMQXの詳細：* [*EMQX Enterprise：エンタープライズMQTTプラットフォーム*](https://www.emqx.com/ja/products/emqx) diff --git a/ja/202307/one-click-deploying-emqx-mqtt-broker-on-aws-using-terraform.md b/ja/202307/one-click-deploying-emqx-mqtt-broker-on-aws-using-terraform.md index a9dbacb0..77cd964e 100644 --- a/ja/202307/one-click-deploying-emqx-mqtt-broker-on-aws-using-terraform.md +++ b/ja/202307/one-click-deploying-emqx-mqtt-broker-on-aws-using-terraform.md @@ -1,6 +1,6 @@ ## はじめに -[MQTT](https://www.emqx.com/en/mqtt-guide)は、デバイス間の通信を可能にするためにIoT（モノのインターネット）アプリケーションで一般的に使用されている軽量メッセージングプロトコルです。オープンソースのMQTTブローカーとして人気の[EMQX](https://www.emqx.io/)は、MQTTメッセージングに高いスケーラビリティ、信頼性、セキュリティを提供します。 +[MQTT](https://www.emqx.com/en/mqtt-guide)は、デバイス間の通信を可能にするためにIoT（モノのインターネット）アプリケーションで一般的に使用されている軽量メッセージングプロトコルです。オープンソースのMQTTブローカーとして人気の[EMQX](https://github.com/emqx/emqx)は、MQTTメッセージングに高いスケーラビリティ、信頼性、セキュリティを提供します。 Infrastructure as Code（IaC）ツールとして普及しているTerraformを使用することで、AWS上のEMQX MQTT Brokerのデプロイを自動化し、MQTTインフラのセットアップと管理を容易にすることができます。 diff --git a/ja/202307/sparkplug-3-0-advancements-and-formalization-in-mqtt-for-iiot.md b/ja/202307/sparkplug-3-0-advancements-and-formalization-in-mqtt-for-iiot.md index fd74398f..ce521055 100644 --- a/ja/202307/sparkplug-3-0-advancements-and-formalization-in-mqtt-for-iiot.md +++ b/ja/202307/sparkplug-3-0-advancements-and-formalization-in-mqtt-for-iiot.md @@ -81,7 +81,7 @@ Sparkplug Compatibility Programは、ソフトウェアおよびハードウェ Sparkplug 3.0は、IIoTアプリケーション向けのMQTT Sparkplugプロトコルに大幅な進化と正式化をもたらします。改善された明快さ、明確な仕様、MQTT 5.0との整合性により、Sparkplug 3.0は、相互運用性の強化、効率的なデータ同期、産業環境への合理的な導入を実現します。IIoTエコシステムが進化し続ける中、Sparkplug 3.0はIIoTネットワーク内で信頼性が高くスケーラブルな通信を行うための堅牢で標準化されたソリューションを提供します。 -世界有数の[オープンソースMQTTブローカー](https://www.emqx.io/)であるEMQXは、すべてのSparkplug 3.0メッセージトラフィックを管理するインフラの主要コンポーネントです。IIoTコネクティビティ・サーバーである[Neuronは、エッジ・ノード](https://neugates.io/)として機能し、OTデバイスのスマート化を支援し、非同期でSparkplug 3.0メッセージを報告することができます。 +世界有数の[オープンソースMQTTブローカー](https://github.com/emqx/emqx)であるEMQXは、すべてのSparkplug 3.0メッセージトラフィックを管理するインフラの主要コンポーネントです。IIoTコネクティビティ・サーバーである[Neuronは、エッジ・ノード](https://neugates.io/)として機能し、OTデバイスのスマート化を支援し、非同期でSparkplug 3.0メッセージを報告することができます。 diff --git a/ja/202307/the-ultimate-guide-to-mqtt-broker-comparison.md b/ja/202307/the-ultimate-guide-to-mqtt-broker-comparison.md index 91271e7e..25d49fb0 100644 --- a/ja/202307/the-ultimate-guide-to-mqtt-broker-comparison.md +++ b/ja/202307/the-ultimate-guide-to-mqtt-broker-comparison.md @@ -42,7 +42,7 @@ MQTT ブローカー・アーキテクチャには、集中型と分散型があ ### EMQX -[EMQX](https://www.emqx.io/)は現在、IoTアプリケーション向けの最もスケーラブルなMQTTブローカーである。ミリ秒以下のレイテンシーで1秒間に数百万のMQTTメッセージを処理し、単一のクラスタ内で1億以上のクライアント間のメッセージングを可能にする。EMQXはMQTT 5.0および3.xに準拠しており、分散IoTネットワークに最適で、クラウド、Microsoft Azure、Amazon Web Services、Google Cloud上で実行できる。このブローカーはTLS/SSL上でMQTTを実装でき、PSK、JWT、X.509などの認証メカニズムをサポートしている。Mosquittoとは異なり、EMQXはCLI、HTTP API、ダッシュボードによるクラスタリングをサポートしている。 +[EMQX](https://github.com/emqx/emqx)は現在、IoTアプリケーション向けの最もスケーラブルなMQTTブローカーである。ミリ秒以下のレイテンシーで1秒間に数百万のMQTTメッセージを処理し、単一のクラスタ内で1億以上のクライアント間のメッセージングを可能にする。EMQXはMQTT 5.0および3.xに準拠しており、分散IoTネットワークに最適で、クラウド、Microsoft Azure、Amazon Web Services、Google Cloud上で実行できる。このブローカーはTLS/SSL上でMQTTを実装でき、PSK、JWT、X.509などの認証メカニズムをサポートしている。Mosquittoとは異なり、EMQXはCLI、HTTP API、ダッシュボードによるクラスタリングをサポートしている。
@@ -175,7 +175,7 @@ MQTTブローカーを選ぶ際のポイントや評価プロセスを支援す ## EMQX: 世界で最もスケーラブルなMQTTブローカー -[EMQX](https://www.emqx.io/) は1.15万のスターを獲得している人気のMQTTブローカーの一つで、GitHub上にあるEMQXプロジェクトは2012年に立ち上げられ、Apache version 2.0のライセンス下にある。EMQXは大規模にスケーラブルなソフトリアルタイムシステムを構築するためのErlang/OTPプログラミング言語で書かれている。 +[EMQX](https://github.com/emqx/emqx) は1.15万のスターを獲得している人気のMQTTブローカーの一つで、GitHub上にあるEMQXプロジェクトは2012年に立ち上げられ、Apache version 2.0のライセンス下にある。EMQXは大規模にスケーラブルなソフトリアルタイムシステムを構築するためのErlang/OTPプログラミング言語で書かれている。 EMQXはMQTT 5.0、MQTT-SN、[MQTT over QUIC](https://www.emqx.com/ja/blog/mqtt-over-quic)のような高度な機能をサポートする世界で最もスケーラブルなMQTTブローカーです。ハイアベイラビリティと水平方向スケーラビリティのためにマスタレスクラスタリングをサポートしています。最新版のEMQX 5.0は、23ノードのシングルクラスタで100万の同時MQTT接続を確立することができます diff --git a/ja/202308/emqx-single-node-supports-5m-connections.md b/ja/202308/emqx-single-node-supports-5m-connections.md index 7a219a40..dc76cef3 100644 --- a/ja/202308/emqx-single-node-supports-5m-connections.md +++ b/ja/202308/emqx-single-node-supports-5m-connections.md @@ -22,7 +22,7 @@ | ブローカー | デプロイメント | バージョン | OS | CPU | メモリ | クラウドホストモデル | | ---------------------------- | ------- | ------ | -------- | --- | ---- | --------------------------------------------------------------------------------------------------------------------------------- | -| [EMQX](https://www.emqx.io/) | 単一ノード | 5.0.21 | RHEL 8.5 | 64C | 128G | [hfc6.16xlarge](https://www.alibabacloud.com/help/ja/ecs/user-guide/cpu-options-of-instance-families-with-high-clock-speeds#hfc6) | +| [EMQX](https://github.com/emqx/emqx) | 単一ノード | 5.0.21 | RHEL 8.5 | 64C | 128G | [hfc6.16xlarge](https://www.alibabacloud.com/help/ja/ecs/user-guide/cpu-options-of-instance-families-with-high-clock-speeds#hfc6) | ## テストツール diff --git a/ja/202308/iiot-explained-examples-technologies-benefits-and-challenges.md b/ja/202308/iiot-explained-examples-technologies-benefits-and-challenges.md index 5fa54886..af46b2c2 100644 --- a/ja/202308/iiot-explained-examples-technologies-benefits-and-challenges.md +++ b/ja/202308/iiot-explained-examples-technologies-benefits-and-challenges.md @@ -140,7 +140,7 @@ IIoT技術の急速な進化により、業界ではスキルのギャップが EMQは、業界をリードするMQTTブローカーEMQXとの緊密な連携のもと、産業データオペレーションとデータ中心の自動化のための軽量コネクティビティサーバー[Neuron](https://www.emqx.com/ja/products/neuronex)を提供しています。Neuronは、IIoTにおいて、接続性の簡素化、データ統合の強化、リアルタイム通信と分析を可能にする重要なメリットを提供します。 -IIoTの管理に従事している場合、[EMQX](https://www.emqx.io/ja)とNeuronは以下を支援できます。 +IIoTの管理に従事している場合、[EMQX](https://github.com/emqx/emqx)とNeuronは以下を支援できます。 1. IT接続性: EMQXブローカーは、40を超えるクラウドサービスとエンタープライズシステムとのシームレスな統合のための多様なデータブリッジを提供します。このため、異なるアプリケーション間でのデータアクセスが容易になり、カスタムブリッジ開発のコストと複雑さが削減されます。EMQXはMySQL、PostgreSQL、MongoDBなどのデータベース、Redis、Oracle、SAP、Kafkaなどの技術との統合をサポートしています。この豊富なコネクタにより、IIoTエコシステム内での効率的なIT接続性とデータ交換が実現します。 diff --git a/ja/202308/mqtt-sparkplug-in-action-a-step-by-step-tutorial.md b/ja/202308/mqtt-sparkplug-in-action-a-step-by-step-tutorial.md index cb17ae34..f88c9a33 100644 --- a/ja/202308/mqtt-sparkplug-in-action-a-step-by-step-tutorial.md +++ b/ja/202308/mqtt-sparkplug-in-action-a-step-by-step-tutorial.md @@ -6,7 +6,7 @@ ## EMQXとNeuron：不可欠なコンポーネント -[EMQX](https://www.emqx.io/)はSparkplugプロトコルをサポートする人気的な[MQTTブローカー](https://www.emqx.com/ja/blog/the-ultimate-guide-to-mqtt-broker-comparison)であり、Neuronは産業用デバイスからデータを収集し、アプリケーション用にSparkplugメッセージを生成するために使用できる産業用IoTプラットフォームである。 +[EMQX](https://github.com/emqx/emqx)はSparkplugプロトコルをサポートする人気的な[MQTTブローカー](https://www.emqx.com/ja/blog/the-ultimate-guide-to-mqtt-broker-comparison)であり、Neuronは産業用デバイスからデータを収集し、アプリケーション用にSparkplugメッセージを生成するために使用できる産業用IoTプラットフォームである。 [Neuron](https://neugates.io/)はデバイスからデータを収集し、そのデータに基づいてEMQXブローカにSparkplugメッセージを発行して変更を報告します。EMQXは、関連するSparkplugトピックをサブスクライブしているアプリケーションにメッセージを転送します。しかし、EMQXはルールエンジンを通してSparkplugメッセージをデコードすることができる。メッセージはその後、データプラットフォームや履歴の永続ストレージなどに使用される。 @@ -27,7 +27,7 @@ ## EMQXのインストール -EMQX MQTTブローカーをダウンロードし、サーバーまたはマシンにインストールする。EMQXはコミュニティ版を提供しており、ウェブサイトから無料でダウンロードできる。ウェブサイト[https://www.emqx.io/](https://www.emqx.io/)、ドキュメントに従ってください。 +EMQX MQTTブローカーをダウンロードし、サーバーまたはマシンにインストールする。EMQXはコミュニティ版を提供しており、ウェブサイトから無料でダウンロードできる。ウェブサイト[https://github.com/emqx/emqx](https://github.com/emqx/emqx)、ドキュメントに従ってください。
diff --git a/ja/202308/use-mqtt-with-raspberry-pi.md b/ja/202308/use-mqtt-with-raspberry-pi.md index c2b8df74..2c92c748 100644 --- a/ja/202308/use-mqtt-with-raspberry-pi.md +++ b/ja/202308/use-mqtt-with-raspberry-pi.md @@ -2,7 +2,7 @@ [ラズベリー・パイ](https://www.raspberrypi.org/)は、イギリスのラズベリー・パイ財団によって開発されたARMベースの小型シングルボードコンピュータである。このボードはUSBインターフェースとイーサネットインターフェースを備えており、キーボード、マウス、ネットワークケーブルを接続することができる。このボードはPCの基本機能を持ち、ラズベリーパイはWi-Fi、Bluetooth、多数のGPIOを統合しており、教育、ファミリー・エンターテインメント、IoTなどで広く使用されている。 -このプロジェクトでは、Pythonを使ってRaspberry Pi上にシンプルな[MQTTクライアント](https://www.emqx.com/ja/blog/mqtt-client-tools)を書き、このクライアントと[MQTTブローカー](https://www.emqx.io/ja)間の接続、サブスクリプション、メッセージング、その他の機能を実装する。 +このプロジェクトでは、Pythonを使ってRaspberry Pi上にシンプルな[MQTTクライアント](https://www.emqx.com/ja/blog/mqtt-client-tools)を書き、このクライアントと[MQTTブローカー](https://github.com/emqx/emqx)間の接続、サブスクリプション、メッセージング、その他の機能を実装する。 ## Raspberry Pi MQTTプロジェクトの準備 diff --git a/ja/202309/advanced-features-of-mqtt-topics.md b/ja/202309/advanced-features-of-mqtt-topics.md index aee1fc22..283ff2f4 100644 --- a/ja/202309/advanced-features-of-mqtt-topics.md +++ b/ja/202309/advanced-features-of-mqtt-topics.md @@ -67,7 +67,7 @@ sensor/bedroom/1/temperature で始まるトピックは、`$SYS/`主に MQTT ブローカーの実行ステータス、統計、クライアントのオンライン/オフライン イベントなどに関するメタデータを取得するために使用されるシステム トピックです。`$SYS/`トピックは MQTT 仕様では定義されていません。ただし、ほとんどの[MQTT ブローカーは](https://www.emqx.com/ja/blog/the-ultimate-guide-to-mqtt-broker-comparison)この[推奨事項](https://github.com/mqtt/mqtt.org/wiki/SYS-Topics)に従っています。 -たとえば、[EMQX は](https://www.emqx.io/ja)、次のトピックを通じてクラスターのステータスの取得をサポートしています。 +たとえば、[EMQX は](https://github.com/emqx/emqx)、次のトピックを通じてクラスターのステータスの取得をサポートしています。 | トピック | 説明 | | :------------------------------ | :-------------------------- | diff --git a/ja/202309/demonstrate-mqtt-5-0-features-using-mqttx-cli.md b/ja/202309/demonstrate-mqtt-5-0-features-using-mqttx-cli.md index e26b5541..a725f0a4 100644 --- a/ja/202309/demonstrate-mqtt-5-0-features-using-mqttx-cli.md +++ b/ja/202309/demonstrate-mqtt-5-0-features-using-mqttx-cli.md @@ -1,6 +1,6 @@ [MQTT](https://www.emqx.com/ja/blog/the-easiest-guide-to-getting-started-with-mqtt)は、現在IoT分野で最も一般的な通信プロトコルです。最新バージョンの5.0は、すでに2019年にリリースされています。以前のバージョンと比較すると、5.0はセッション期限、理由コード、共有サブスクリプション、リクエスト/レスポンスなど、現代のIoTアプリケーションのニーズに合った新機能が追加されており、今ではほとんどのIoT企業が選択するバージョンとなっています。 -MQTT 5.0の全機能を包括的に理解していただくために、この記事では5.0で導入されたそれぞれの新機能を順に説明し、[EMQX](https://www.emqx.io/ja)での使用方法を[MQTTX CLI](https://mqttx.app/ja)ツールを使用してデモンストレーションします。コマンドをコピー&ペーストすることで、記事のサンプルを簡単に実行できます。 +MQTT 5.0の全機能を包括的に理解していただくために、この記事では5.0で導入されたそれぞれの新機能を順に説明し、[EMQX](https://github.com/emqx/emqx)での使用方法を[MQTTX CLI](https://mqttx.app/ja)ツールを使用してデモンストレーションします。コマンドをコピー&ペーストすることで、記事のサンプルを簡単に実行できます。 める前に、以下の準備が必要です: diff --git a/ja/202309/how-to-set-parameters-when-establishing-an-mqtt-connection.md b/ja/202309/how-to-set-parameters-when-establishing-an-mqtt-connection.md index 7be8ef03..360a044f 100644 --- a/ja/202309/how-to-set-parameters-when-establishing-an-mqtt-connection.md +++ b/ja/202309/how-to-set-parameters-when-establishing-an-mqtt-connection.md @@ -44,7 +44,7 @@ IoT メッセージング シナリオに非常に適した QUIC の利点に基 **MQTT over WebSocketの接続** -WebSocket 接続を使用する場合は、接続アドレスにパスも含める必要があります。[EMQX](http://www.emqx.io/ja)に構成されたデフォルトのパスは です`/mqtt`。 +WebSocket 接続を使用する場合は、接続アドレスにパスも含める必要があります。[EMQX](https://github.com/emqx/emqx)に構成されたデフォルトのパスは です`/mqtt`。 たとえば、`ws://broker.emqx.io:8083/mqtt`は WebSocket ベースの MQTT 接続アドレス、 は`wss://broker.emqx.io:8083/mqtt`WebSocket ベースの MQTT セキュア接続アドレスです。 diff --git a/ja/202309/simulating-the-future-crafting-iot-scenarios-with-chatgpt-and-mqttx.md b/ja/202309/simulating-the-future-crafting-iot-scenarios-with-chatgpt-and-mqttx.md index 3be9aec0..f2120f8e 100644 --- a/ja/202309/simulating-the-future-crafting-iot-scenarios-with-chatgpt-and-mqttx.md +++ b/ja/202309/simulating-the-future-crafting-iot-scenarios-with-chatgpt-and-mqttx.md @@ -17,7 +17,7 @@ AIテクノロジーが進化するにつれ、ChatGPTのような先進的な 1. データ要件の分析: 当初、IoTシナリオのデータニーズを評価し、シミュレートする必要があるデータのカテゴリ、構造、およびフォーマットを特定します。 2. ChatGPTを使用したシミュレーションスクリプトの生成: 評価に基づき、高度な大規模言語モデルであるChatGPTを利用して、MQTTXのシミュレーションスクリプトを作成します。 これにより、スクリプト作成が大幅に簡素化されるだけでなく、データコンテンツの品質と真正性が保証されます。 -3. MQTTXによるデータ送信のシミュレーション: ChatGPTによって生成されたスクリプトを使用して、MQTTXはデバイスデータの送信をシミュレートし、[EMQX](https://www.emqx.io/)などのMQTTサーバーと連携します。 +3. MQTTXによるデータ送信のシミュレーション: ChatGPTによって生成されたスクリプトを使用して、MQTTXはデバイスデータの送信をシミュレートし、[EMQX](https://github.com/emqx/emqx)などのMQTTサーバーと連携します。 ![Incorporating Generative AI into MQTT Data Testing](https://assets.emqx.com/images/f6980406bc52b273f7a6c5b60eed54a4.png) @@ -25,7 +25,7 @@ AIテクノロジーが進化するにつれ、ChatGPTのような先進的な - ChatGPT: データのシミュレーションスクリプト生成に特化したAIツールです。 強力な自然言語処理機能により、MQTTXのための正確でリアルなシミュレーションスクリプトを作成できます。 - [MQTTX](https://mqttx.app/ja)**:** 高機能なMQTTクライアントツールで、カスタムスクリプト機能により、メッセージの送受信のためのデバイスシミュレーションが可能です。 -- [EMQX](https://www.emqx.io/ja)**:** シミュレートデータの安定した送信を保証する、推奨のMQTTサーバー。 +- [EMQX](https://github.com/emqx/emqx)**:** シミュレートデータの安定した送信を保証する、推奨のMQTTサーバー。 以下のセクションでは、データシミュレーションテストをすぐに開始する方法をガイドします。 diff --git a/ja/202309/the-smart-manufacturing-revolution.md b/ja/202309/the-smart-manufacturing-revolution.md index 0b4e44cc..0139fd0a 100644 --- a/ja/202309/the-smart-manufacturing-revolution.md +++ b/ja/202309/the-smart-manufacturing-revolution.md @@ -120,7 +120,7 @@ IIoT は、通信して意思決定を行うことができるインテリジェ ## EMQX を使用した IIoT のソリューション -EMQは、業界トップクラスの[MQTTブローカー](https://www.emqx.io/ja)との深い統合を特徴とする、産業データオペレーションとデータ中心の自動化のための軽量なコネクティビティサーバー[Neuron](https://www.emqx.com/ja/products/neuronex)を提供しています。Neuronは、スマートな製造業にいくつかの大きなメリットをもたらし、IIoTコネクティビティを簡素化し、データ統合を強化し、リアルタイム通信と分析を可能にします。 +EMQは、業界トップクラスの[MQTTブローカー](https://github.com/emqx/emqx)との深い統合を特徴とする、産業データオペレーションとデータ中心の自動化のための軽量なコネクティビティサーバー[Neuron](https://www.emqx.com/ja/products/neuronex)を提供しています。Neuronは、スマートな製造業にいくつかの大きなメリットをもたらし、IIoTコネクティビティを簡素化し、データ統合を強化し、リアルタイム通信と分析を可能にします。 賢いメーカーであれば、[EMQX](https://www.emqx.com/ja/products/emqx)と Neuron が次の点で役立ちます。 diff --git a/ja/202309/what-is-the-mqtt-protocol.md b/ja/202309/what-is-the-mqtt-protocol.md index e6c59c2d..9ea61e24 100644 --- a/ja/202309/what-is-the-mqtt-protocol.md +++ b/ja/202309/what-is-the-mqtt-protocol.md @@ -155,7 +155,7 @@ MQTT 5.0 についてさらに詳しく知りたい場合は、MQTT 5.0 の重 MQTT ブローカーは、クライアントによって開始された接続を受信し、クライアントによって送信されたメッセージを他の適格なクライアントに転送する責任を負います。成熟した MQTT ブローカーは、大規模な接続と数百万のメッセージ スループットをサポートできるため、IoT ビジネス プロバイダーがビジネス機能に集中し、信頼性の高い MQTT アプリケーションを迅速に作成できるようになります。 -[EMQX は、](https://www.emqx.io/)広く使用されている IoT 用の大規模分散 MQTT ブローカーです。2013 年に GitHub でオープンソース リリースされて以来、世界中で 1,000 万回以上ダウンロードされ、接続されている IoT キー デバイスの累計数は 1 億台を超えています。 +[EMQX は、](https://github.com/emqx/emqx)広く使用されている IoT 用の大規模分散 MQTT ブローカーです。2013 年に GitHub でオープンソース リリースされて以来、世界中で 1,000 万回以上ダウンロードされ、接続されている IoT キー デバイスの累計数は 1 億台を超えています。 次の Docker コマンドを使用して EMQX 5.0 オープンソース バージョンをインストールして体験できます。 diff --git a/ja/202310/leveraging-enhanced-authentication-for-mqtt-security.md b/ja/202310/leveraging-enhanced-authentication-for-mqtt-security.md index 3bd4b417..cc7d91c8 100644 --- a/ja/202310/leveraging-enhanced-authentication-for-mqtt-security.md +++ b/ja/202310/leveraging-enhanced-authentication-for-mqtt-security.md @@ -71,7 +71,7 @@ SCRAM 認証を開始するには、クライアントは、認証方法属性 強化された認証により、ユーザーはさらに多くの ID 検証方法を導入できるようになります。特定のニーズに適した認証方法を選択し、システムのセキュリティをさらに強化できます。 -[EMQX](https://www.emqx.io/ja)は、高いスケーラビリティと可用性で知られる広く使用されている MQTT ブローカーとして、ユーザーのセキュリティの確保を常に優先してきました。[パスワードベースの認証](https://docs.emqx.com/en/emqx/v5.0/access-control/authn/pwoverview.html)に加えて、EMQX は強化認証もサポートしています。ユーザーは、EMQX による SCRAM 認証を有効にして、MQTT インフラストラクチャのセキュリティ レベルを向上させることができます。詳細については、「[MQTT 5.0 強化認証」](https://docs.emqx.com/en/emqx/v5.0/access-control/authn/scram.html#configure-with-dashboard)を参照してください。 +[EMQX](https://github.com/emqx/emqx)は、高いスケーラビリティと可用性で知られる広く使用されている MQTT ブローカーとして、ユーザーのセキュリティの確保を常に優先してきました。[パスワードベースの認証](https://docs.emqx.com/en/emqx/v5.0/access-control/authn/pwoverview.html)に加えて、EMQX は強化認証もサポートしています。ユーザーは、EMQX による SCRAM 認証を有効にして、MQTT インフラストラクチャのセキュリティ レベルを向上させることができます。詳細については、「[MQTT 5.0 強化認証」](https://docs.emqx.com/en/emqx/v5.0/access-control/authn/scram.html#configure-with-dashboard)を参照してください。 diff --git a/ja/202310/mqtt-session.md b/ja/202310/mqtt-session.md index a0b09b4b..c1a16ff7 100644 --- a/ja/202310/mqtt-session.md +++ b/ja/202310/mqtt-session.md @@ -30,7 +30,7 @@ Clean Session は、セッション状態のライフサイクルを制御する > ***注:** Persistent Session は、クライアントが固定クライアント ID を使用して再度接続した場合にのみ再開できます。クライアント ID が動的である場合、接続が成功した後に新しい Persistent Session が作成されます。* -以下は、[オープンソースの MQTT ブローカー EMQX ](https://www.emqx.io/)のダッシュボードです。図の接続は切断されていることがわかりますが、 Persistent Session であるため、ダッシュボードには引き続き表示できます。 +以下は、[オープンソースの MQTT ブローカー EMQX ](https://github.com/emqx/emqx)のダッシュボードです。図の接続は切断されていることがわかりますが、 Persistent Session であるため、ダッシュボードには引き続き表示できます。 ![MQTT Connections](https://assets.emqx.com/images/f66ac8daa11ef2ff5df6b466cd81b510.png) diff --git a/ja/202310/securing-mqtt-with-username-and-password-authentication.md b/ja/202310/securing-mqtt-with-username-and-password-authentication.md index 1796a09d..4279c76e 100644 --- a/ja/202310/securing-mqtt-with-username-and-password-authentication.md +++ b/ja/202310/securing-mqtt-with-username-and-password-authentication.md @@ -72,7 +72,7 @@ MQTT では、パスワードベースの認証は一般に、ユーザー名と ## まとめ -結論として、パスワードベースの認証は、[MQTT 接続を](https://www.emqx.com/ja/blog/how-to-set-parameters-when-establishing-an-mqtt-connection)保護し、IoT システムの整合性を保護する上で重要な役割を果たします。IoT 開発者は、パスワードの選択、保存、送信に関するベスト プラクティスに従い、ブルート フォース攻撃などの一般的な問題を認識することで、MQTT ネットワークのセキュリティを確保できます。[EMQX は](https://www.emqx.io/ja)、高い拡張性と可用性を備え、広く使用されている MQTT ブローカーとして、ユーザーの IoT システムのセキュリティを保証するために、[パスワードベースの認証を](https://docs.emqx.com/en/emqx/v5.0/access-control/authn/authn.html)含むさまざまなセキュリティ対策も提供します。 +結論として、パスワードベースの認証は、[MQTT 接続を](https://www.emqx.com/ja/blog/how-to-set-parameters-when-establishing-an-mqtt-connection)保護し、IoT システムの整合性を保護する上で重要な役割を果たします。IoT 開発者は、パスワードの選択、保存、送信に関するベスト プラクティスに従い、ブルート フォース攻撃などの一般的な問題を認識することで、MQTT ネットワークのセキュリティを確保できます。[EMQX は](https://github.com/emqx/emqx)、高い拡張性と可用性を備え、広く使用されている MQTT ブローカーとして、ユーザーの IoT システムのセキュリティを保証するために、[パスワードベースの認証を](https://docs.emqx.com/en/emqx/v5.0/access-control/authn/authn.html)含むさまざまなセキュリティ対策も提供します。 しかし、パスワードベースの認証は、MQTTで利用可能な数多くの認証方法の1つに過ぎず、必ずしもすべてのユースケースに最適とは限らないことに注意することが重要です。例えば、デジタル証明書やOAuth 2.0などのより高度な方法は、特定のシナリオにおいてより強力なセキュリティを提供する可能性があります。したがって、IoT 開発者は、最新の認証方法を常に把握し、特定のアプリケーションのニーズに最も適したものを選択することが重要です。 diff --git a/ja/202311/fortifying-mqtt-communication-security-with-ssl-tls.md b/ja/202311/fortifying-mqtt-communication-security-with-ssl-tls.md index f760c6b3..e537b01f 100644 --- a/ja/202311/fortifying-mqtt-communication-security-with-ssl-tls.md +++ b/ja/202311/fortifying-mqtt-communication-security-with-ssl-tls.md @@ -85,7 +85,7 @@ TLS を実装するには、通信のセキュリティを確保するために TLS は、インターネット上で安全に通信する方法を提供します。デバイスごとに専用のシークレットを使用し、正しい認証方法を選択すると、TLS のセキュリティを強化できます。このブログで提供されている実装のベスト プラクティスに従うことで、TLS の能力を最大限に活用して、より安全な IoT プラットフォームを構築できます。 -[EMQX に](https://www.emqx.io/ja)は、一方向/双方向認証、X.509 証明書、ロード バランス SSL、その他多くのセキュリティ証明書を含む TLS/SSL のサポートが組み込まれています。EMQX でサポートされるすべてのプロトコルに対して SSL/TLS を有効にし、TLS を使用するように EMQX が提供する HTTP API を構成できます。さらに詳しいガイダンスが必要な場合は、EMQX が提供するものを引き続き調べてください。 +[EMQX に](https://github.com/emqx/emqx)は、一方向/双方向認証、X.509 証明書、ロード バランス SSL、その他多くのセキュリティ証明書を含む TLS/SSL のサポートが組み込まれています。EMQX でサポートされるすべてのプロトコルに対して SSL/TLS を有効にし、TLS を使用するように EMQX が提供する HTTP API を構成できます。さらに詳しいガイダンスが必要な場合は、EMQX が提供するものを引き続き調べてください。 - [EMQX Enterprise の一方向認証](https://www.emqx.com/en/blog/emqx-server-ssl-tls-secure-connection-configuration-guide) - [EMQX Enterprise の双方向認証](https://www.emqx.com/en/blog/enable-two-way-ssl-for-emqx) diff --git a/ja/202311/improve-the-reliability-and-security-of-mqtt-broker-with-rate-limit.md b/ja/202311/improve-the-reliability-and-security-of-mqtt-broker-with-rate-limit.md index d6aac2c7..fa4e66b7 100644 --- a/ja/202311/improve-the-reliability-and-security-of-mqtt-broker-with-rate-limit.md +++ b/ja/202311/improve-the-reliability-and-security-of-mqtt-broker-with-rate-limit.md @@ -64,7 +64,7 @@ listeners.tcp.default { レート制限は、トラフィックを制限してバランスをとることにより、攻撃者が悪意を持ってサーバー リソースを消費し、サービスの信頼性に影響を与えることを防ぎます。また、通常のビジネス変更によるトラフィックの変動にも対応できます。ただし、一部の攻撃では攻撃者が有効なリクエストを送信する必要がなく、レート制限を回避する可能性があります。したがって、サーバー側でもこれらの潜在的なセキュリティ脅威を特定する必要があります。 -[EMQX は](https://www.emqx.io/ja)、ユーザーのセキュリティを優先しながら、高い拡張性と可用性を提供する、広く使用されている[MQTT ブローカー](https://www.emqx.com/ja/blog/the-ultimate-guide-to-mqtt-broker-comparison)です。EMQX では、リスナーごとに異なるレート制限を簡単に設定し、指定したクライアント ID または IP をバックリストに追加できます。詳細については、EMQX の[レート制限](https://docs.emqx.com/zh/emqx/v5.0/rate-limit/rate-limit.html)と[ブラックリスト機能のドキュメントを参照してください。](https://docs.emqx.com/zh/emqx/v5.0/access-control/blacklist.html) +[EMQX は](https://github.com/emqx/emqx)、ユーザーのセキュリティを優先しながら、高い拡張性と可用性を提供する、広く使用されている[MQTT ブローカー](https://www.emqx.com/ja/blog/the-ultimate-guide-to-mqtt-broker-comparison)です。EMQX では、リスナーごとに異なるレート制限を簡単に設定し、指定したクライアント ID または IP をバックリストに追加できます。詳細については、EMQX の[レート制限](https://docs.emqx.com/zh/emqx/v5.0/rate-limit/rate-limit.html)と[ブラックリスト機能のドキュメントを参照してください。](https://docs.emqx.com/zh/emqx/v5.0/access-control/blacklist.html) diff --git a/ja/202312/how-to-use-mqtt-in-php.md b/ja/202312/how-to-use-mqtt-in-php.md index d1bcabe4..decccd6a 100644 --- a/ja/202312/how-to-use-mqtt-in-php.md +++ b/ja/202312/how-to-use-mqtt-in-php.md @@ -1,6 +1,6 @@ [PHP](https://www.php.net/)は、広く使われているオープンソースの多目的スクリプト言語で、HTMLに埋め込むことができ、特にWeb開発に適しています。 -この記事では、PHPプロジェクトで`php-mqtt/client`クライアントライブラリを使って、[MQTTクライアント](https://www.emqx.com/ja/blog/mqtt-client-tools)と[MQTTブローカー](https://www.emqx.io/)間の接続、サブスクライブ、サブスクライブ解除、メッセージの受信と送信の機能を実装する方法について主に紹介します。 +この記事では、PHPプロジェクトで`php-mqtt/client`クライアントライブラリを使って、[MQTTクライアント](https://www.emqx.com/ja/blog/mqtt-client-tools)と[MQTTブローカー](https://github.com/emqx/emqx)間の接続、サブスクライブ、サブスクライブ解除、メッセージの受信と送信の機能を実装する方法について主に紹介します。 ## MQTTクライアントライブラリの選択 diff --git a/ja/202312/subscription-identifier-and-subscription-options.md b/ja/202312/subscription-identifier-and-subscription-options.md index e2945474..c59565b8 100644 --- a/ja/202312/subscription-identifier-and-subscription-options.md +++ b/ja/202312/subscription-identifier-and-subscription-options.md @@ -34,7 +34,7 @@ SUBSCRIBE パケットには、 Subscription Identifier を 1 つだけ含める ## デモ -1. Web ブラウザで[MQTTX Web](http://www.emqx.io/ja)にアクセスします。 +1. Web ブラウザで[MQTTX Web](https://mqttx.app/ja)にアクセスします。 2. [MQTT over WebSocket](https://www.emqx.com/ja/blog/connect-to-mqtt-broker-with-websocket)接続を作成し、[無料のパブリック MQTT サーバー](https://www.emqx.com/ja/mqtt/public-mqtt5-broker)に接続します。 diff --git a/ja/202403/bridging-opc-ua-data-to-mqtt-for-iiot.md b/ja/202403/bridging-opc-ua-data-to-mqtt-for-iiot.md index 4c26097e..d41753b4 100644 --- a/ja/202403/bridging-opc-ua-data-to-mqtt-for-iiot.md +++ b/ja/202403/bridging-opc-ua-data-to-mqtt-for-iiot.md @@ -4,7 +4,7 @@ [Neuron](https://neugates.io/)は、標準プロトコルまたはデバイス固有のプロトコルを使用して幅広い産業デバイスに接続できる最新の[産業用IoT](https://www.emqx.com/ja/blog/iiot-explained-examples-technologies-benefits-and-challenges)接続サーバーです。Neuronは、リソースが限られたさまざまなIoTエッジハードウェアデバイスで動作するように設計された軽量の産業プロトコルゲートウェイソフトウェアであり、データ中心の自動化装置からのデータアクセスに関する課題を解決することを主な目的としています。 -[EMQX](https://www.emqx.io/ja) は、分散型オープンソースの[MQTTブローカー](https://www.emqx.com/ja/blog/the-ultimate-guide-to-mqtt-broker-comparison)です。世界で最もスケーラブルなMQTTメッセージングサーバーとして、EMQXは大量のIoTデバイスへの効率的で信頼性の高い接続を提供し、メッセージとイベントストリームの高性能でリアルタイムな移動と処理を可能にし、ビジネスクリティカルなIoTプラットフォームやアプリケーションの迅速な構築をユーザーに支援します。 +[EMQX](https://github.com/emqx/emqx) は、分散型オープンソースの[MQTTブローカー](https://www.emqx.com/ja/blog/the-ultimate-guide-to-mqtt-broker-comparison)です。世界で最もスケーラブルなMQTTメッセージングサーバーとして、EMQXは大量のIoTデバイスへの効率的で信頼性の高い接続を提供し、メッセージとイベントストリームの高性能でリアルタイムな移動と処理を可能にし、ビジネスクリティカルなIoTプラットフォームやアプリケーションの迅速な構築をユーザーに支援します。 Neuronの南向きOPC UAドライバーによって収集および集約されたOPC UAデータソースは、MQTTプロトコルに変換され、EMQX MQTTブローカーに伝送されます。後者はそれらをさまざまざまな分散アプリケーションに配布します。 diff --git a/ja/202403/bridging-twincat-data-to-mqtt.md b/ja/202403/bridging-twincat-data-to-mqtt.md index 99445c17..e6374285 100644 --- a/ja/202403/bridging-twincat-data-to-mqtt.md +++ b/ja/202403/bridging-twincat-data-to-mqtt.md @@ -16,7 +16,7 @@ Beckhoff ADSプラグインを使用すると、ユーザーはTwinCAT PLCから ### MQTTメッセージの処理にはEMQXを使用します -[EMQX](https://www.emqx.io/ja)は、高性能でスケーラブルな世界最先端のオープンソース分散型IoT [MQTTブローカー](https://www.emqx.com/ja/blog/the-ultimate-guide-to-mqtt-broker-comparison)です。EMQXは、大量のIoTデバイスに効率的で信頼性の高い接続を提供し、メッセージとイベントフローデータの高性能なリアルタイム移動と処理を可能にし、ユーザーが迅速に重要なビジネス向けのIoTプラットフォームとアプリケーションを構築できるよう支援します。 +[EMQX](https://github.com/emqx/emqx)は、高性能でスケーラブルな世界最先端のオープンソース分散型IoT [MQTTブローカー](https://www.emqx.com/ja/blog/the-ultimate-guide-to-mqtt-broker-comparison)です。EMQXは、大量のIoTデバイスに効率的で信頼性の高い接続を提供し、メッセージとイベントフローデータの高性能なリアルタイム移動と処理を可能にし、ユーザーが迅速に重要なビジネス向けのIoTプラットフォームとアプリケーションを構築できるよう支援します。 EMQXはブリッジングアーキテクチャのブローカーコンポーネントであり、NeuronEXはTwinCAT PLCからデータを収集し、データをMQTTメッセージとしてブローカーに転送します。NeuronEXからMQTTメッセージを受信した後、EMQXはデータを転送したり、さらなる処理を行ったりします。 diff --git a/ja/202403/coap-protocol.md b/ja/202403/coap-protocol.md index 065ce034..592a1f08 100644 --- a/ja/202403/coap-protocol.md +++ b/ja/202403/coap-protocol.md @@ -133,7 +133,7 @@ CoAPとMQTTは共存できます。制約されたCoAPネットワークが外 CoAPは、低消費電力、低電力デバイス間の通信をサポートする、制約されたネットワーク向けにサポートします。CoAPは制限されたネットワーク内ではうまく機能しますが、デバイスが外部ネットワークと通信する必要がある場合には不足しています。さらに、CoAPはリソース処理センターのサポートが欠けており、M2Mネットワークモデルに設計されています（CoAPベースのLwM2Mプロトコルは、リソース登録やリソースサービスなどの概念を導入しています）。 -この問題は、オープンソースのMQTTメッセージブローカーである[EMQX](https://www.emqx.io/ja)を使用することで解決できます。外部ネットワークと通信する必要があるCoAPデバイスにとって、EMQXをブローカーとして使用することは、以下を容易にします： +この問題は、オープンソースのMQTTメッセージブローカーである[EMQX](https://github.com/emqx/emqx)を使用することで解決できます。外部ネットワークと通信する必要があるCoAPデバイスにとって、EMQXをブローカーとして使用することは、以下を容易にします： - デバイスの認証と信頼できないデバイスからのデータの拒否。 - リソース権限の管理、異なるデバイスに対する異なるリソース読み取り/書き込み権限の指定を含む。 diff --git a/ja/202403/knx-protocol.md b/ja/202403/knx-protocol.md index 23922769..c7280d29 100644 --- a/ja/202403/knx-protocol.md +++ b/ja/202403/knx-protocol.md @@ -105,7 +105,7 @@ KNX Virtualには、シミュレートされたKNXバスに接続された10種 ### MQTTメッセージを処理するEMQX -[EMQX](https://www.emqx.io/ja)は、高性能とスケーラビリティを備えた世界をリードするオープンソースの分散MQTTブローカーです。大量のIoTデバイスに対して効率的で信頼性の高い接続を提供し、リアルタイムのメッセージおよびイベントフローデータの移動と処理を可能にし、ユーザーがクリティカルなビジネス用のIoTプラットフォームとアプリケーションを迅速に構築できるよう支援します。 +[EMQX](https://github.com/emqx/emqx)は、高性能とスケーラビリティを備えた世界をリードするオープンソースの分散MQTTブローカーです。大量のIoTデバイスに対して効率的で信頼性の高い接続を提供し、リアルタイムのメッセージおよびイベントフローデータの移動と処理を可能にし、ユーザーがクリティカルなビジネス用のIoTプラットフォームとアプリケーションを迅速に構築できるよう支援します。 EMQXはブリッジアーキテクチャのブローカーコンポーネントであり、NeuronはKNXデバイスからデータを収集し、MQTTメッセージとしてブローカーにデータを送信します。NeuronからMQTTメッセージを受信した後、EMQXはデータを転送したり、さらに処理を行ったりします。 diff --git a/ja/202403/opc-ua-protocol.md b/ja/202403/opc-ua-protocol.md index e4a0b0f5..dba37bec 100644 --- a/ja/202403/opc-ua-protocol.md +++ b/ja/202403/opc-ua-protocol.md @@ -196,7 +196,7 @@ Pub-Subのセキュリティはクライアント/サーバーよりも少し複 [Neuron](https://neugates.io/)は、標準プロトコルまたはデバイス固有のプロトコルを使用して幅広い産業デバイスに接続できる最新の産業用IoT接続サーバーです。Neuronは、リソースが限られたさまざまなIoTエッジハードウェアデバイスで動作するように設計された軽量の産業プロトコルゲートウェイソフトウェアであり、データ中心の自動化装置からのデータアクセスに関する課題を解決することを主な目的としています。 -[EMQX](https://www.emqx.io/ja) は、分散型の[オープンソースMQTTブローカー](https://www.emqx.com/en/blog/a-comprehensive-comparison-of-open-source-mqtt-brokers-in-2023)です。世界で最もスケーラブルなMQTTメッセージングサーバーとして、EMQXは大量のIoTデバイスへの効率的で信頼性の高い接続を提供し、メッセージとイベントストリームの高性能でリアルタイムな移動と処理を可能にし、ビジネスクリティカルなIoTプラットフォームやアプリケーションの迅速な構築をユーザーに支援します。 +[EMQX](https://github.com/emqx/emqx) は、分散型の[オープンソースMQTTブローカー](https://www.emqx.com/en/blog/a-comprehensive-comparison-of-open-source-mqtt-brokers-in-2023)です。世界で最もスケーラブルなMQTTメッセージングサーバーとして、EMQXは大量のIoTデバイスへの効率的で信頼性の高い接続を提供し、メッセージとイベントストリームの高性能でリアルタイムな移動と処理を可能にし、ビジネスクリティカルなIoTプラットフォームやアプリケーションの迅速な構築をユーザーに支援します。 Neuronの南向きOPC UAドライバーによって収集および集約されたOPC UAデータソースは、MQTTプロトコルに変換され、EMQX MQTTブローカーに伝送されます。後者はそれらをさまざまな分散アプリケーションに配布します。 diff --git a/ja/202403/using-mqtt-in-flutter.md b/ja/202403/using-mqtt-in-flutter.md index b749625c..9f77db29 100644 --- a/ja/202403/using-mqtt-in-flutter.md +++ b/ja/202403/using-mqtt-in-flutter.md @@ -38,7 +38,7 @@ import 'package:mqtt_client/mqtt_client.dart'; ### MQTTブローカーへの接続 -この記事では、[EMQX Cloud](https://www.emqx.com/ja/cloud)によって運用・管理されている[MQTTブローカー](https://www.emqx.io/ja/mqtt/public-mqtt5-broker)を使用します。 EMQX Cloudは、EMQによってリリースされた[MQTT IoTクラウド](https://www.emqx.com/ja/cloud)サービスプラットフォームで、オールインワンの運用・保守とユニークな分離環境での**MQTT 5.0**へのアクセスサービスを提供します。 +この記事では、[EMQX Cloud](https://www.emqx.com/ja/cloud)によって運用・管理されている[MQTTブローカー](https://www.emqx.com/ja/mqtt/public-mqtt5-broker)を使用します。 EMQX Cloudは、EMQによってリリースされた[MQTT IoTクラウド](https://www.emqx.com/ja/cloud)サービスプラットフォームで、オールインワンの運用・保守とユニークな分離環境での**MQTT 5.0**へのアクセスサービスを提供します。 - ブローカー: `broker.emqx.io` - TCPポート: **1883** diff --git a/ja/202404/bridging-modbus-data-to-mqtt-for-iiot.md b/ja/202404/bridging-modbus-data-to-mqtt-for-iiot.md index 9c197237..bc027694 100644 --- a/ja/202404/bridging-modbus-data-to-mqtt-for-iiot.md +++ b/ja/202404/bridging-modbus-data-to-mqtt-for-iiot.md @@ -67,11 +67,11 @@ MQTTの主な利点は以下の通りです。 ModbusからMQTTへのブリッジアーキテクチャは、主に2つのコンポーネントで構成されています。Modbusデータソースと[MQTTブローカー](https://www.emqx.com/ja/blog/the-ultimate-guide-to-mqtt-broker-comparison)です。データソースはModbusデータをMQTTブローカーに送信し、MQTTブローカーはそのデータを受信して転送します。このプロセスを実現するには、2つの重要な要素が必要です。1つはModbusプロトコルをMQTTに変換し、データをMQTTブローカーに送信するエッジデバイスであり、もう1つはMQTTメッセージを処理するMQTTブローカーです。 -本記事では、[Neuron](https://neugates.io/)と[EMQX](https://www.emqx.io/ja)を使用してブリッジプロセスを実装します。 +本記事では、[Neuron](https://neugates.io/)と[EMQX](https://github.com/emqx/emqx)を使用してブリッジプロセスを実装します。 [Neuron](https://neugates.io/)は、標準またはプロプライエタリなプロトコルを使用してさまざまな産業用デバイスを接続できる、現代的な[産業用IoT](https://www.emqx.com/ja/blog/iiot-explained-examples-technologies-benefits-and-challenges)接続サーバーです。産業用IoTプラットフォームとデバイス間の相互接続を実現します。軽量な産業用ソフトウェアであるNeuronは、リソースが限られたさまざまなIoTエッジハードウェアデバイス上で実行できます。データを中心とした自動化機器データの統一的なアクセスの難しさを解決し、スマートマニュファクチャリングのための基盤を提供することを目的としています。 -[EMQX](https://www.emqx.io/ja)は、高性能でスケーラブルな、世界をリードするオープンソースの分散型IoT MQTT ブローカーです。EMQXは、大量のIoTデバイスに効率的で信頼性の高い接続を提供し、メッセージとイベントフローデータのリアルタイムな移動と処理を高性能でサポートすることで、ユーザーが重要なビジネス向けのIoTプラットフォームとアプリケーションを迅速に構築できるようにします。 +[EMQX](https://github.com/emqx/emqx)は、高性能でスケーラブルな、世界をリードするオープンソースの分散型IoT MQTT ブローカーです。EMQXは、大量のIoTデバイスに効率的で信頼性の高い接続を提供し、メッセージとイベントフローデータのリアルタイムな移動と処理を高性能でサポートすることで、ユーザーが重要なビジネス向けのIoTプラットフォームとアプリケーションを迅速に構築できるようにします。 以下の図は、Neuronがエッジからデータをどのように収集し、それをMQTTに変換してEMQXにアップロードするかを示しています。 @@ -266,7 +266,7 @@ MQTTXを起動したら、メインページの**+新しい接続**をクリッ ![Oil Production Data Acquisition](https://assets.emqx.com/images/5c5a23f0474e9305c1f4d0026176f01b.png) -Neuron と [EMQX](https://www.emqx.io/ja)、[eKuiper](https://ekuiper.org/)、[EMQX ECP](https://www.emqx.com/en/products/emqx-ecp) などの他の EMQ 製品を組み合わせた全体的なソリューションは、石油業界に以下のようなメリットをもたらします。 +Neuron と [EMQX](https://github.com/emqx/emqx)、[eKuiper](https://ekuiper.org/)、[EMQX ECP](https://www.emqx.com/en/products/emqx-ecp) などの他の EMQ 製品を組み合わせた全体的なソリューションは、石油業界に以下のようなメリットをもたらします。 - フロントエンドを軽量化し、バックエンドを重視するシステムアーキテクチャにより、現場の機器とシステムの運用・保守コストを削減できます。 - MQTTのIoTプロトコルを主なデータ収集・伝送方式として利用することで、生産データをリアルタイムに報告し、業務システムの応答性を向上させます。 diff --git a/ja/202404/mqtt-and-kafka.md b/ja/202404/mqtt-and-kafka.md index d87d4df8..b818deca 100644 --- a/ja/202404/mqtt-and-kafka.md +++ b/ja/202404/mqtt-and-kafka.md @@ -36,7 +36,7 @@ IoTプラットフォームでMQTTとKafkaを統合する際には、いくつ ### EMQX Kafkaデータ統合 -[EMQX](https://www.emqx.io)は、Kafkaデータ統合機能を通じてKafkaとのシームレスな統合を提供する人気の[MQTTブローカー](https://www.emqx.com/ja/blog/the-ultimate-guide-to-mqtt-broker-comparison)です。MQTTとKafkaの間のブリッジとして、EMQXは2つのプロトコル間のスムーズな通信を可能にします。 +[EMQX](https://github.com/emqx/emqx)は、Kafkaデータ統合機能を通じてKafkaとのシームレスな統合を提供する人気の[MQTTブローカー](https://www.emqx.com/ja/blog/the-ultimate-guide-to-mqtt-broker-comparison)です。MQTTとKafkaの間のブリッジとして、EMQXは2つのプロトコル間のスムーズな通信を可能にします。 この統合により、プロデューサー（Kafkaへのメッセージ送信）とコンシューマー（Kafkaからのメッセージ受信）の2つの役割でKafkaへのデータブリッジを作成できます。EMQXでは、これらの役割のいずれかでデータブリッジを確立できます。双方向のデータ伝送機能により、EMQXはアーキテクチャ設計の柔軟性を提供します。さらに、低遅延と高スループットを提供し、効率的で信頼性の高いデータブリッジ操作を保証します。