The best way to get started is to read the Key Concepts section and then take one of the many tutorials offered in the Developers documentation.
Use the following command in the mimik-edge-cli tool to retrieve the Access Token:
mimik-edge-cli account get-edge-access-token -t <DEVELOPER_ID_TOKEN> --use-mid-v1
You get the <DEVELOPER_ID_TOKEN> from your account in the mimik Developer Console as shown below in Figure 1.
NOTE: The Developer ID Token is labeled as ID Token in the mimik Developer Console UI.
To learn more read the mimik-edge-cli reference here.
mimik technology is not a network mesh. Instead, our platform enables a service mesh, which allows service-to-service communication.
This is the major differentiation. Other IoT technologies require a local gateway, to which IoT devices connect, and all communication among these devices is proxy�ed by the gateway.
With our technology, every device can be turned into an independent server, and thus service-to-service communication happens without any gateway.
allows a microservice to run on a device, and this turns the device to a server. The microservice running on the device can also serve personal information, and of course, only permitted entity has access to this information. The microservice can also act as a consumer of another microservice, aka service-to-service communication.
No, there is no need for rooting a device.
No routing protocol needs to be modified.
In fact, we provide service discovery on over linkLocal, account, and proximity. These service discoveries give you the address to directly access the service, and in the case if the device is behind the firewall, the address is to a secure tunnel.
mimik technology enables running serverless microservices on any compatible OS, and these serverless microservice serves RESTful APIs over HTTPS, which is a TCP based protocol.
mimik technology can work over IP based network connections, such as Wifi, ethernet, and cellular (LTE/5G) connection.
The throughput is determined by the underlying network connection that the device currently is using. In other words, if two devices have direct linkLocal network connection, the throughput really is the entire local network bandwidth.
If two devices do not have a direct link-local network connection, but have internet connection, The communication is tunneled via mimik tunnelling service, and the throughput is now limited by both the upload internet speed of device A and download internet speed of device B.
Because mimik is using serverless microservice, resource is only consumed when an API calls happen. In other words, one can host as much serverless microservice as the storage allows.
If devices are under the same local network, the devices can still be discovered among themselves via the egdeEngine supernode technology. The elected supernode for the link local network contains the local IP of these devices. In other words, if one service on device A want to communicate with another service on device B, service on device A will go to the supernode to find the local IP address of service on device B. After that service on device A will connect to service on device B using the local IP address of device B.
All are equally treated.