This document discusses the complexity of developing and maintaining software at the edge in IoT environments. It proposes that using a traditional centralized approach to develop software for distributed edge infrastructure is problematic. The solution presented is a distributed platform that extends from data centers to IoT gateways and devices, building a peer-to-peer network. This allows software to run seamlessly from edge data centers to edge devices, ensuring consistency even with unstable connections and offline tolerance.

1. Simplifying IoT by Solving Software Complexity at the Edge
by Samy Fodil
samy@taubyte.com

2. OVERVIEW
During this webinar we will explore why it’s hard to write and maintain
software at the Edge, then propose some solutions.

3. TREND (1/2)
Source: seamster.io

4. TREND (2/2)
Source: seamster.io

5. PROBLEM (1/2)
As the need to run software on or in
close proximity to connected devices
become ubiquitous(*)
, development,
deployment and routing complexity
increases exponentially.
For companies of all sizes, tackling those
issues is time consuming and capital
intensive.
Edge Computing Landscape report Q1 2020, Topio Network (*)

6. PROBLEM (2/2)
IoT connectivity is quite unstable. When it
happens it results in data and money
loss.
Ensuring continuous operation and
consistency even through high latency
and unstable links!

7. WHY?
Today, the Edge, a distributed infrastructure, is being tapped into using
the traditional centralized approach, and that’s the source of the
problem!

8. SOLUTION (1/2)
A distributed platform that extends from data centers to IoT gateways
and devices.

9. SOLUTION (2/2)
Building a peer-to-peer software-defined
network.
Popular examples:
● BitTorrent
● Etherium

10. A CATEGORY-DEFINING PLATFORM THAT
ENABLES THE TRUE POTENTIALOF THE EDGE

11. PRODUCT (1/3)
With an embeddable stack, our platform seamlessly extends from our
Edge Data Centers all the way to customer's Edge devices, building a
peer-to-peer, natively-distributed, software-defined network.

12. PRODUCT (2/3)
Our platform has the intelligence to:
● Version and replicate data
● Ensure consistency even through high
latency and unstable links
● Dynamically provision proximity
serverless services:
○ Computing
○ Storage
○ Database
○ Ledger
○ Message brokers

13. PRODUCT (3/3)
● Software on our stack runs on a mesh
of inter-connected nodes
● Computation and storage happens
exactly where it should
● There are no:
○ Intermediaries
○ Single points-of-failure; this
means performance, flexibility
and resilience

14. How does it work?
Let’s dive into some internals!

15. OFFLINE TOLERANCE (1/3)
● Disconnections are quite common in IoT
● When that happens, our services running on the disconnected node will still
be available locally

16. OFFLINE TOLERANCE (2/3)
● When connectivity is back, the node rejoins with no service interruption
○ Worrying about outages of the network or individual nodes is a thing of
the past!

17. OFFLINE TOLERANCE (3/3)
Software built with Taubyte’s framework are magically partition-tolerant
and always available!

18. TELEMETRY STORAGE

19. OBJECT STORAGE

20. STORAGE
Our stack will automatically insure deduplication and immutability of
data!

21. FUTURE
According to IDC the number of connected devices will be
Over 42 Billion by 2025
That is a lot of complexity!

22. Q & A

23. MQTT
Public MQTT service for development:
● public.mqtt.taubyte.com
○ MQTT
○ MQTTS
● No authentication necessary

24. EARLY ACCESS
You think we can help you?
● Early access
○ Restricted to B2B
● Reach out to
○ joseph@taubyte.com