eaf6863d1c
|
||
|---|---|---|
| config | ||
| test/locust | ||
| utils/postman | ||
| .gitignore | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| MAINTAINERS | ||
| README.md | ||
| docker-compose-local-config.yml | ||
| docker-compose.yml | ||
README.md
Mainflux
About
Mainflux is modern open source and patent-free IoT cloud platform written in Go and based on microservices.
It allows device, user and application connections over various network protocols, like HTTP, MQTT, WebSocket and CoAP, making a seamless bridge between them. It is used as the IoT middleware for building complex IoT solutions.
Mainflux is built with <3 by Mainflux team and community contributors.
N.B. Mainlux is uder heavy development and not yet suitable for professional deployments
Two Flavours
Mainflux comes in two flawours:
- Mainflux Lite - simplified monolithic system
- Maiflux Full (or just Mainflux) - the full-blown multi-service system
If you are new to Mainflux it Mainflux Lite is a place to start. It has most of the services offered by Mainflux, but bundled in one monolithic binary.
Mainflux Lite is suitable for quick and simple deployments and for development.
On the other hand, Mainflux Full (in further text refered simply as Mainflux) is a production system, based on several independent and inter-connected services run in a separate Docker containers.
Install/Deploy
Installation and deployment of Mainflux IoT cloud is super-easy:
- Clone the repo:
git clone https://github.com/Mainflux/mainflux.git && cd mainflux
- Start the Docker composition:
docker-compose up
This will automatically download Docker images from Mainflux Docker Hub and deploy the composition.
If you need to modify these Docker images, you will have to look at appropriate repos in the Mainflux project GitHub - look for the repos starting with prefix mainflux-<protocol>-server.
System Architecture
Mainflux IoT cloud is composed of several components, i.e. microservices:
- Mainflux Core
- Authentication and Authorization Server
- HTTP API Server
- MQTT API Server
- WebSocket API Server
- NATS PUB/SUB Broker
- Mongo Database
- Dashflux UI
Following diagram illustrates the architecture:
And here is the matrix describes the functionality of each microservice in the system and gives the location of the code repositories:
| Microservice | Function | GitHub repo |
|---|---|---|
| Mainflux Core | Core Server | mainflux-core-server |
| Auth Server | Authentication and Authorization | mainflux-auth-server |
| HTTP API Server | HTTP API Server | mainflux-http-server |
| MQTT API Server | MQTT API Server | mainflux-mqtt-server |
| WS API Server | WS API Server | mainflux-ws-server |
| NATS | PUB/SUB Broker | nats-io/gnatsd |
| MongDB | Device Context Storage | mongodb/mongo |
| Dashflux | Dashboard UI | dashflux |
These components are packaged and deployed in a set of Docker containers maintained by Mainflux team, with images uploaded to Mainflux Docker Hub page.
Docker composition that constitues Mainflux IoT infrastructure is defined in the docker-compose.yml.
Features
An extensive (and incomplete) list of features includes:
- Responsive and scalable architecture based on a set of microservices
- Set of clean APIs: HTTP RESTful, MQTT, WebSocket and CoAP
- SDK - set of client libraries for many HW platforms in several programming languages: C/C++, JavaScript, Go and Python
- Device management and provisioning and OTA FW updates
- Highly secured connections via TLS and DTLS
- Enhanced and fine-grained security via Reverse Proxy, OAuth 2.0 identity management and RBAC Authorization Server.
- LwM2M standard compliance
- oneM2M adapter
- Easy deployment and high system scalability via Docker images
- Clear project roadmap, extensive development ecosystem and highly skilled developer community
- And many more
Documentation
Development documentation can be found on our Mainflux GitHub Wiki.
Community
Mailing lists
- mainflux-dev - developers related. This is discussion about development of Mainflux IoT cloud itself.
- mainflux-user - general discussion and support. If you do not participate in development of Mainflux cloud infrastructure, this is probably what you're looking for.