diff --git a/_data/mqtt-broker/docs-home.yml b/_data/mqtt-broker/docs-home.yml index 93df138554..5a6ec4a7c6 100644 --- a/_data/mqtt-broker/docs-home.yml +++ b/_data/mqtt-broker/docs-home.yml @@ -39,6 +39,8 @@ toc: path: /docs/mqtt-broker/user-guide/ui/users/ - title: Mail Server path: /docs/mqtt-broker/user-guide/ui/mail-server/ +- title: Subscriptions + path: /docs/mqtt-broker/subscription/ - title: Troubleshooting path: /docs/mqtt-broker/troubleshooting/ - title: Release Notes diff --git a/_layouts/pricing.html b/_layouts/pricing.html index 3e56b01aeb..db82a98868 100644 --- a/_layouts/pricing.html +++ b/_layouts/pricing.html @@ -96,7 +96,7 @@ } function setActivePricingSection(sectionId) { - var activateSelectProduct = sectionId === 'thingsboard-pe-options' || sectionId === 'trendz-options'; + var activateSelectProduct = sectionId === 'thingsboard-pe-options' || sectionId === 'trendz-options' || sectionId === 'mqtt-broker-options'; $("li.menu-item").removeClass("active"); $("li.menu-item#menu-item-"+sectionId).addClass("active"); hidePricingContent(); diff --git a/docs/contact-us.md b/docs/contact-us.md index 45c118d111..94848dae55 100644 --- a/docs/contact-us.md +++ b/docs/contact-us.md @@ -100,6 +100,7 @@ notitle: "true" + diff --git a/docs/mqtt-broker/subscription.md b/docs/mqtt-broker/subscription.md new file mode 100644 index 0000000000..81779df34e --- /dev/null +++ b/docs/mqtt-broker/subscription.md @@ -0,0 +1,157 @@ +--- +layout: docwithnav-mqtt-broker +title: TBMQ Subscription plans definition +description: Features and advantages of TBMQ subscription payment model + +--- + +TBMQ provides dedicated subscription plans based on the **pay-as-you-go** model. + +### Limits + +Please see table below to compare the limits of the subscription plans. The values are monthly limits, unless stated otherwise. + +
Parameter name | +Maker | +Prototype | +Startup | +Business | +Description | +
Sessions | +1K | +2K | +5K | +10K | +Maximum number of client sessions managed by the broker, including both connected sessions and persistent sessions that are temporarily disconnected but still maintained by the broker for quick reconnection | +
TMPS | +1K | +2K | +5K | +10K | +Total throughput of messages processed per second, including both incoming and outgoing MQTT_PUBLISH packets. The acknowledgment packets to the MQTT_PUBLISH packets for QoS 1 and 2 levels are not included | +
Application clients | +5 | +10 | +25 | +50 | +Maximum number of persistent Application clients managed by the broker, including both connected and temporarily disconnected ones | +
Device persistent messages rate limits | +50 | +100 | +250 | +500 | +Total number of messages processed per second for all Device persistent clients | +
Application topic size | +1 GB | +1 GB | +1 GB | +1 GB | +Maximum topic size for Application client to store persisted messages | +
Application topic TTL | +1 day | +1 day | +1 day | +1 day | +"Time to live" parameter for messages stored in Application topics | +
Device persisted messages storage | +50 | +100 | +250 | +500 | +Maximum number of persisted messages per Device client | +
Device persisted messages TTL | +1 day | +1 day | +1 day | +1 day | +"Time to live" parameter for messages stored for Device persisted clients | +
Stats TTL | +1 month | +1 month | +1 month | +1 month | +"Time to live" parameter for statistics persistence. This includes metrics visible on the UI: sessions, subscriptions, incoming messages, outgoing messages, etc. | +
Session TTL | +1 day | +1 day | +1 day | +1 day | +"Time to live" parameter for persistent offline session. After this time the disconnected sessions will be deleted from the broker | +
Client incoming messages rate limit | +Up to 10 per second, not exceeding 300 per minute | +Up to 10 per second, not exceeding 300 per minute | +Up to 10 per second, not exceeding 300 per minute | +Up to 10 per second, not exceeding 300 per minute | +Total number of incoming messages per client | +
Client outgoing messages rate limit | +Up to 10 per second, not exceeding 300 per minute | +Up to 10 per second, not exceeding 300 per minute | +Up to 10 per second, not exceeding 300 per minute | +Up to 10 per second, not exceeding 300 per minute | +Total number of outgoing messages per non-persistent subscriber client with QoS = 0 ("AT_MOST_ONCE") | +
In-flight messages | +100 | +100 | +100 | +100 | +Maximum number of in-flight (pending acknowledgment) messages allowed per client | +
Client pre-connect messages | +100 | +100 | +100 | +100 | +Maximum queue size for messages received per client during the client's active connection period | +
Message size | +1 MB | +1 MB | +1 MB | +1 MB | +Maximum payload size of MQTT_PUBLISH packet | +
Uptime SLA | +99.95% | +99.99% | +99.99% | +99.99% | +Represents the percentage of time a broker is expected to be fully operational and accessible | +
Customer may cancel the subscription and purchase a perpetual license. @@ -1168,7 +1363,7 @@ selfManagedPlan:
It can be your advantage for a quick start with the platform. These 10 hours can be used for consulting, training, or development services. Training sessions imply pre-defined topics, while Consulting may cover various technical questions, platform configurations, or your Use Case-related issues. The above services are conducted online. Alternatively, these 10 hours can be used to support you in the PoC, MVP, or ready-for-market solutions development by a dedicated development unit from ThingsBoard. @@ -1182,7 +1377,6 @@ selfManagedPlan:
@@ -1354,5 +1548,71 @@ selfManagedPlan:
+ Dedicated plan features the deployment of a dedicated MQTT broker cluster on the ThingsBoard cloud, expertly managed by the TBMQ team. + The cluster comprises several TBMQ nodes, ensuring high availability and uninterrupted service. + A dedicated load balancer is included to seamlessly distribute your incoming traffic across multiple targets. + Additionally, each plan includes sessions and message limits, as well as persistence limits to store essential data during offline periods. + It provides a 99.99% uptime SLA. Focus on your solution while we manage the servers for you on our cloud. +
++ BYOC (Bring Your Own Cloud) deployment option allows you to leverage your existing cloud infrastructure while integrating our powerful MQTT broker cluster. + This flexibility ensures that you can maintain control over your cloud environment, optimize costs, and meet specific regulatory or compliance requirements. + The TBMQ team is responsible for managing the cluster and providing technical support. +
++ TMPS refers to the total number of messages processed per second by the TBMQ cluster. + This metric includes both incoming and outgoing messages but counts only 'MQTT PUBLISH' packets. + For instance, if you have 100 devices each sending 10 messages per second, the incoming volume would be 1,000 messages per second. + If there are 2 subscribers consuming these messages, resulting in 2,000 outgoing messages per second, the TMPS would be 3,000. + TMPS provides a comprehensive measure of the messaging throughput handled by the TBMQ cluster, ensuring efficient and reliable communication for your IoT applications. +
++ Application client is a specialized type of client designed for scenarios with high message subscription volumes. + It uses a dedicated message queue and consumer to ensure high performance and enables message persistence when the subscriber is offline. + This makes it well-suited for scenarios where reliable message delivery is necessary, and message loss is unacceptable. +
++ Device client is a standard type of client that can be configured to be persistent or non-persistent based on the connection settings. + Persistent device messages are stored in a database while their corresponding device subscribers are offline. + The limit for device persistent messages is configured per TBMQ cluster, rather than per individual client, ensuring efficient resource management. +
++ For BYOC (Bring Your Own Cloud) deployment, contact us to discuss your specific needs and preferences. + We will work with you to determine the required infrastructure, load patterns, and cloud options that best suit your environment. + Additionally, we will assess your cluster requirements and Service Level Agreement (SLA) needs to ensure optimal performance and reliability. +
++ Yes, TBMQ subscriptions have sessions, messages, and storage limits. See subscription documentation for more details. +
+