Add SuperMQ and Magistrala merge announcement blog post#112
Add SuperMQ and Magistrala merge announcement blog post#112dborovcanin merged 4 commits intoabsmach:mainfrom
Conversation
Signed-off-by: nyagamunene <stevenyaga2014@gmail.com>
| - IoT Platform | ||
| - Open Source | ||
| category: announcement | ||
| featured: true |
There was a problem hiding this comment.
Removed featured flag from all the other blogs.
|
|
||
| ## A quick history | ||
|
|
||
| [Magistrala](https://github.com/absmach/magistrala) started as a full-featured open-source IoT platform — handling device connectivity, multi-tenancy, access control, the Rules Engine, Alarms, Reports, and more. Over time, we extracted its core messaging and infrastructure layer into a separate project: [SuperMQ](https://github.com/absmach/supermq). |
There was a problem hiding this comment.
Also, mention that now we have a separate core messaging called FluxMQ. So now, we have a stack that consists of Magistrala, FluxMQ, Hardware components, and Propeller. Give a short description of each and relevant add links:
- FluxMQ - cloud and edge messaging backbone - a versatile, efficient and high-performance message broker that runs on edge and cloud, clusters and scales and supports event store for internal service synchronization.
- Magistrala - a cloud IoT platform framework, that provides mentioned features and integrates with FluxMQ for messaging to provide a flexible framework for building IoT solutions.
- Hardware (S0) - modular IoT gateway solutions for smart metering, industrial IoT, and edge computing. S0 module and Base Board deliver multi-protocol connectivity with open-source hardware and professional support.
- Propeller - a cutting-edge orchestrator for WebAssembly workloads across the Cloud-Edge continuum.
Something like this.
There was a problem hiding this comment.
Let's give this post a little bit more of a storytelling note - first, explain why we split, what was the intended stack, what's the reasons we are merging, what's FluxMQ and what's the new stack. In that order. Maybe a diagram would be nice.
Signed-off-by: nyagamunene <stevenyaga2014@gmail.com>
|
|
||
| ## A quick history | ||
|
|
||
| [Magistrala](https://github.com/absmach/magistrala) started as a full-featured open-source IoT platform — handling device connectivity, multi-tenancy, access control, the Rules Engine, Alarms, Reports, and more. Over time, we extracted its core messaging and infrastructure layer into a separate project: [SuperMQ](https://github.com/absmach/supermq). |
There was a problem hiding this comment.
Let's give this post a little bit more of a storytelling note - first, explain why we split, what was the intended stack, what's the reasons we are merging, what's FluxMQ and what's the new stack. In that order. Maybe a diagram would be nice.
Signed-off-by: nyagamunene <stevenyaga2014@gmail.com>
* Add SuperMQ and Magistrala merge announcement blog post * Add cover image and fix image path for merge announcement blog Signed-off-by: nyagamunene <stevenyaga2014@gmail.com> * Remove featured flag and add Abstract Machines stack description Signed-off-by: nyagamunene <stevenyaga2014@gmail.com> * address comments Signed-off-by: nyagamunene <stevenyaga2014@gmail.com>
What type of PR is this?
What does this do?
Which issue(s) does this PR fix/relate to?
Have you included tests for your changes?
Did you document any new/modified features?
Notes