Skip to main content
Select Page

Problem: connectivity disruptions. Solution: Active Replication Fabric.

Small footprint eXtremeDB offers a reliable solution to mitigate IoT connectivity issues.

eXtremeDB Active Replication Fabric™ mitigates IoT connectivity issues and solves issues for developers.

Bidirectional replication

The Active Replication Fabric APIs allow replication upstream from edge to gateway to server, and downstream from server to edge devices.

Intermittent connections

Data flow is fully automated through the Active Replication Fabric allowing developers to mitigate IoT connectivity issues.

Multi-tier replication (e.g. edge-to-gateway-to-gateway-to-cloud)

The Active Replication Fabric APIs allow device-based applications to collect data, then transmit the collected data when connected. Multi-tier means from an edge device to gateway to a server – however many hops are needed according to the network topology.

Compression to maximize limited bandwidth networks

eXtremeDB offers low-level network compression as well as run-length encoding (RLE) compression for columnar (time-series) data reducing storage space and improving speed.

Security

eXtremeDB protects its data at rest through sophisticated AES encryption algorithms and in transmission by employing integrated SSL/TLS protocols for its communication channels.

Use the eXtremeDB xPanel net viewer for easier IoT data management

How it works

Edge nodes‘ physical connectivity can be intermittent, and constrained. Some popular protocols have limited bandwidth (ZigBee, NFC and RFID, LPWAN, Bluetooth Low Energy, etc.). Edge device connectivity can be intermittent because of the physical device location (e.g. a mobile device) or because the device is battery operated and connects at certain predefined times. From the standpoint of data management, the unpredictable connectivity means that fully integrated support for “push” and “pull” protocols is important to preserve data collected at the edge.

We use the term storage containers (opens in a new tab) for databases maintained on edge devices that are mapped to an upstream database.

The eXtremeDB Active Replication Fabric (opens in a new tab) allows device-based applications to collect data, which is then automatically transmitted when connected.  Likewise, it also allows replicating server-side data to IoT devices; a common task for new device configuration and provisioning.  Data flow is fully automated through the Active Replication Fabric allowing developers to mitigate or even solve IoT connectivity issues.  The APIs provide automatic or on-demand data exchange between collection points and servers.

Whenever an object is inserted, updated, or deleted, a “replication timestamp” is written to the modified object (a separate “record” is maintained for deleted objects). The kernel keeps track of a “global timestamp” that indicates the last data replication event (e.g. when data was last synchronized with the gateway or server). During the next replication event, all records with a replication timestamp later than the “global timestamp” are included in the replication process.

NEW: eXtremeDB Edge Client

The eXtremeDB Edge Client is lightweight transactional storage for highly resource-constrained devices. It extends Active Replication Fabric to systems requiring as little as 8 KB of memory, allowing devices that cannot host a complete embedded database to participate directly in the distributed storage architecture.

The Edge Client supports multiple related data types and preserves referential integrity before replication. Even the smallest devices become full participants in the distributed storage architecture rather than simple message producers.

Light bulb with the filament spelling out the word idea
^

Uses the same schema, data model and transactional semantics as every other eXtremeDB edition, allowing the same application architecture to scale naturally from tiny edge devices to embedded controllers, gateways and enterprise servers.

^
Active Replication Fabric automatically transfers committed transactions to upstream systems whenever connectivity is available.
^
Once delivery has been acknowledged, the local storage is reclaimed, allowing continuous operation with an exceptionally small memory footprint.
^

Uses the same schema, data model and transactional semantics as every other eXtremeDB edition, allowing the same application architecture to scale naturally from tiny edge devices to embedded controllers, gateways and enterprise servers.

^
Active Replication Fabric automatically transfers committed transactions to upstream systems whenever connectivity is available.
^
Once delivery has been acknowledged, the local storage is reclaimed, allowing continuous operation with an exceptionally small memory footprint.
Light bulb with the filament spelling out the word idea

Security features

Billions of IoT devices’ and their storage containers are exposed and inherently vulnerable. Unlike servers, IoT edge devices run in the open and don’t enjoy IT staff attendance, sophisticated firewalls and other security apparatus available at the back-end. 
^

eXtremeDB includes Secure Sockets Layer (SSL) connections, a standard security technology that creates an encrypted link between two endpoints.

^

Cyclic Redundancy Check (CRC) on the database page level detects any unauthorized modification to stored data

^

AES encryption employs a user-provided cipher to prevent access or tampering

^

Support for wolfSSL and Mbed

eXtremeDB knows developers must protect IoT data

Multi-tier network topology and network discovery

eXtremeDB’s Active Replication Fabric supports complex IoT network topology; edge devices connect to gateways, gateways connect to other gateways closer to the cloud, which ultimately connect to servers in the cloud which may themselves consist of many shards/nodes. Further, any eXtremeDB instance in this topology might also be a member of a high availability group or an eXtremeDB Cluster. eXtremeDB’s xPanel dashboard includes a visual network discovery tool that greatly simplifies managing, monitoring and leveraging eXtremeDB’s tracing capability.

^

Learn how eXtremeDB Active Replication Fabric treats distributed database topologies in our online documentation. (opens in a new tab)

^

Review our different distributed database options and objectives

^

Learn what makes eXtremeDB a flexible database for embedded and client/server

eXtremeDB uses Active Replication Fabric to solve IoT connectivity issues
eXtremeDB uses Active Replication Fabric to solve IoT connectivity issues
^

Learn how eXtremeDB Active Replication Fabric treats distributed database topologies in our online documentation. (opens in a new tab)

^

Review our different distributed database options and objectives

^

Learn what makes eXtremeDB a flexible database for embedded and client/server

Data compression

Run-length encoding (opens in a new tab) (RLE) compression can be applied to columnar data (i.e. fields defined as the ‘sequence’ data type).  McObject tests show that activating this feature reduced storage space requirements by 75% and improved the speed of reading the database by 21%.  eXtremeDB also includes a feature for compressing non-columnar data.

eXtremeDB also offers low-level network compression.  IoT networks often use low-bandwidth networks which requires network traffic to be compressed. eXtremeDB implements compression at its System Abstraction Layer (SAL), meaning that compression can be applied to any supported socket type (plain TCP, SSL, local-domain, UDP and others).

^

Learn how eXtremeDB allows for both columnar and row storage in a single database instance

^

Learn more about the eXtremeDB tiny footprint database

^

Review a list of DBMS features to look for if speed matters to your next project

^

Learn what makes eXtremeDB a flexible database for embedded and client/server

Data compression is one way ARF solves IoT connectivity issues

Wherever you need it.

Active Replication fabric means reliable database management for the IoT and support on all platforms from edge to cloud. Learn more about the platform independent eXtremeDB IoT Database Software Development Toolkit.  The eXtremeDB IoT SDK runs on the device, gateway and server, a bundled setup that eliminates the need to learn different DBMS and leverages staff skills.

Related resources

Watch this and other Webinars from the DBMS experts at McObject

Webinars for Professional Developers

Watch to on-demand Webinars, hosted by experts, about proven database management system practices.  Watch “Eliminating Database Corruption“.  Or, “Embedded Databases: Make or Break Technology Choices for High Performance Applications” and others.

^

Watch Scaling IoT Applications – Panel Discussion Part I.
The IoT panel discusses scaling by sensors, performance, users, and geography.

^

Watch Scaling IoT Applications – Panel Discussion Part II.
The IoT panel reviews the tools, architectures and key components used to move the application from prototype to successful deployment.

^

Watch Edge Node Database Systems, the Internet of Things’ Hidden Workhorses.  Topics covered include DBMS architectures, NoSQL, data complexity, and more.

 Review our list of Webinars

White Papers for Professional Developers

We have been testing, improving on, and retesting our software from the beginning in 2001 in order to provide our clients with the best possible data management solutions. Review our research.

Distributed Database Systems and Edge/Fog/Cloud Computing
A distributed database system is one in which the data belonging to a single logical database is distributed to two or more physical databases. Beyond that simple definition, there are a confusing number of possibilities for when, how, and why the data is distributed. Some are applicable to edge and/or fog computing, some others are applicable to fog and/or cloud  computing, and some are applicable across the entire spectrum of edge, fog and cloud computing.

Will the Real IMDS Please Stand Up?
In-memory database systems (IMDSs) have changed the software landscape, enabling “smarter” embedded applications and sparking mergers and acquisitions involving the largest technology companies. But IMDSs’ popularity has sparked a flurry of products falsely claiming to be in-memory database systems. Understanding the distinction is critical to determining the performance, cost and ultimately the success or failure of a solution. This white paper examines specific products, seeking to answer the question, “is it really an in-memory database system?”