diff --git a/.gitignore b/.gitignore index f40fbd8..ddb7f40 100644 --- a/.gitignore +++ b/.gitignore @@ -3,3 +3,5 @@ _site .jekyll-cache .jekyll-metadata vendor +version-2.md +.bundle/ \ No newline at end of file diff --git a/_config.yml b/_config.yml index 797fb89..ca3f098 100644 --- a/_config.yml +++ b/_config.yml @@ -64,4 +64,4 @@ exclude: - Gemfile - Gemfile.lock - CONTRIBUTING.md - \ No newline at end of file + - vendor \ No newline at end of file diff --git a/_sass/style.scss b/_sass/style.scss index c22f5e9..f942a7f 100644 --- a/_sass/style.scss +++ b/_sass/style.scss @@ -608,6 +608,7 @@ main { #homepage-intro { width: 65%; } + .use-case-img { width: 220px !important; height: 125px !important; @@ -682,4 +683,165 @@ main { .use-case-description { margin: 0; } +} + +/* Why MQTT page */ +.minimal-wrapper { + font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; + line-height: 1.7; + --text-primary: #111111; + --text-secondary: #555555; + --border-color: #e5e5e5; + --bg-color: #ffffff; +} + +.minimal-container { + max-width: 900px; + margin: 0 auto; + padding: 60px 20px; + + h1, h2, h3 { color: var(--text-primary); margin-top: 0; } + p { color: var(--text-secondary); } +} + +.minimal-header { + margin-bottom: 60px; + border-bottom: 1px solid var(--border-color); + padding-bottom: 40px; + + h1 { + font-size: 3rem; + font-weight: 600; + letter-spacing: -0.02em; + margin-bottom: 1rem; + line-height: 1.1; + } + + p { + font-size: 1.25rem; + font-weight: 300; + max-width: 700px; + } +} + +.minimal-section { + margin-bottom: 60px; + + h2 { + font-size: 1.5rem; + font-weight: 500; + border-bottom: 1px solid var(--border-color); + padding-bottom: 15px; + margin-bottom: 30px; + } +} + +.business-grid { + display: grid; + grid-template-columns: repeat(auto-fit, minmax(320px, 1fr)); + gap: 24px; + margin-top: 30px; +} + +.business-card { + border: 1px solid var(--border-color); + padding: 30px; + display: flex; + flex-direction: column; + background: var(--bg-color); + + h3 { + font-size: 1.15rem; + font-weight: 600; + margin-bottom: 12px; + line-height: 1.4; + } + + p { + font-size: 0.95rem; + color: var(--text-secondary); + margin-bottom: 24px; + flex-grow: 1; + line-height: 1.6; + } +} + +.proof-point { + font-size: 0.85rem; + font-weight: 600; + color: var(--text-primary); + border-top: 1px solid var(--border-color); + padding-top: 16px; + margin-top: auto; + text-transform: uppercase; + letter-spacing: 0.05em; +} + +.use-case-grid { + display: flex; + flex-wrap: wrap; + gap: 16px; +} + +.use-case-link { + display: inline-block; + padding: 12px 24px; + border: 1px solid var(--border-color); + color: var(--text-primary); + text-decoration: none; + font-weight: 500; + transition: all 0.2s ease; + background: var(--bg-color); + + &:hover { + border-color: var(--text-primary); + background: #f9f9f9; + color: var(--text-primary); + } +} + +.minimal-table-wrapper { + overflow-x: auto; + border: 1px solid var(--border-color); +} + +.minimal-table { + width: 100%; + border-collapse: collapse; + text-align: left; + font-size: 0.95rem; + min-width: 800px; + + th { + background: #fafafa; + padding: 20px; + font-weight: 500; + color: var(--text-primary); + border-bottom: 1px solid var(--border-color); + } + + td { + padding: 20px; + color: var(--text-secondary); + border-bottom: 1px solid var(--border-color); + vertical-align: top; + } + + tr:last-child td { border-bottom: none; } + + .row-header { + font-weight: 600; + color: var(--text-primary); + } + + .mqtt-highlight { + background-color: #f7f7f8; + color: var(--text-primary); + font-weight: 500; + } + + th.mqtt-highlight { + background-color: #eeeeea; + font-weight: 600; + } } \ No newline at end of file diff --git a/_sites/getting-started.md b/_sites/getting-started.md index d827b8b..cf52f9f 100644 --- a/_sites/getting-started.md +++ b/_sites/getting-started.md @@ -6,6 +6,7 @@ description: Useful resources to get you started with MQTT, the standard messagi

Getting started

+
1
diff --git a/_sites/why-mqtt.md b/_sites/why-mqtt.md new file mode 100644 index 0000000..059510a --- /dev/null +++ b/_sites/why-mqtt.md @@ -0,0 +1,117 @@ +--- +title: Why MQTT +index: 0 +description: Learn why technical leaders and CTOs choose MQTT as the standard for scalable, reliable IoT and event-driven architectures. +layout: default +--- + +
+
+
+
+

Architecting for Scale

+

Why modern event-driven architectures rely on MQTT for decoupled system design and guaranteed delivery.

+
+ +
+

Why MQTT for your Business

+ +
+
+

Built to survive the real world

+

Engineered for unreliable networks and constrained edge environments. It reliably delivers data or buffers it until connectivity is restored.

+
Proven in remote factory floors
+
+ +
+

Scale without rebuilding

+

The exceptionally lightweight architecture natively scales from a ten-device pilot to ten million global production devices without re-engineering.

+
Scales linearly to massive fleets
+
+ +
+

Zero vendor lock-in

+

As an open OASIS standard, your core messaging layer remains infrastructure-agnostic, letting you freely migrate workloads between clouds.

+
Interoperable across AWS, Azure & GCP
+
+ +
+

Trusted by industry leaders

+

Deployed globally as the mission-critical foundation for the largest, most demanding consumer and enterprise technologies in existence.

+
Powers BMW's vehicle fleet & Amazon Alexa
+
+ +
+

Secure enterprise connective tissue

+

Intelligently unifies Operational Technology with IT backend systems, backed by strict end-to-end security models across the full stack.

+
The proven bridge for enterprise data lakes
+
+
+
+ +
+

Explore Industry Use Cases

+

Discover how organizations are utilizing MQTT across various sectors to drive operational efficiency and scale.

+ + +
+ +
+

Why Now?

+

MQTT is increasingly used as the edge layer for enterprise architectures, bridging device data to streaming platforms like Apache Kafka and enterprise messaging systems like RabbitMQ. It is designed to fit seamlessly into existing enterprise architectures—acting as the edge-to-cloud bridge—rather than replacing your core backend messaging infrastructure.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CharacteristicMQTTApache KafkaAMQPREST / Webhooks
Core ParadigmIoT & Edge Pub/SubData Streaming / Append LogEnterprise QueuingSynchronous Request/Response
Target EnvironmentUnreliable networks, constrained edgeDatacenter to Datacenter, stable networksBackend microservices, internal VPCsStandard web integrations
Client FootprintExtremely minimal (Microcontroller capable)Heavy (JVM or persistent polling required)Moderate (Complex channel logic required)Heavy (Verbose HTTP payloads)
Connections & ScaleMillions of concurrent active clientsThousands of partitions/clientsTens of thousands of active channelsConstrained heavily by server thread limits
+
+
+
+
+