A NoSQL Database System Architecture for the IoT
Table of contents
- Even as the amount and form of your data has changed drastically over the past decade, the fundamentals of your database system architecture doesn’t have to.
- Moving up the Hierarchy by Leveraging a Distributed Database Architecture
- Creating Solutions as Clear as Water
- The Right NoSQL Database to the Rescue
Even as the amount and form of your data has changed drastically over the past decade, the fundamentals of your database system architecture doesn’t have to.
As far back as the Sears, Roebuck and Company founded at the end of the 19th century, data was always aggregated at the edge and centralized at the company headquarters.
A local retail branch would never send all of its sales receipts back. They would tally sales for the day, week, and month and that’s what they reported to HQ. The individual receipts would be kept in a box, for safekeeping.
As the IoT ushers in a new wave of digital transformation, the question becomes: What do I do with the data? Do you need a new database system architecture? In most cases, the best way to handle the new information is to retain the classic data hierarchy.
Moving up the Hierarchy by Leveraging a Distributed Database Architecture
At the edge, you collect your local data through a kiosk, an application, a sensor or other IoT endpoint. The local data is then pushed to a “regional office” which is usually a NoSQL Database operating on a small server like an ARM Chip or a Raspberry Pi.
The regional office will filter a lot of the data, leaving most of the “individual receipts” at the edge. It will also aggregate it and send it to a more centralized location. The data hierarchy has been in effect for ages, only now it’s digitalized. The data takes on a different form at every step on the hierarchy. It goes from weekly sales in the Midwest to weekly sales for the United States to weekly sales worldwide.
The Internet of Things gives your organization the ability to take in petabytes of data in real time. To keep every bit of data on hand will cost you an arm and a leg – especially if you are storing it on the cloud where they charge you by memory and usage and number of queries!
Filtering, Aggregating, and Processing at the edge saves you time, money, and with the right database, developer resources in setting up the right database architecture.
Creating Solutions as Clear as Water
A good example would be smart meters reading daily water usage for each home. You can have 100,000 smart sensors communicating data for just one town. Every sensor is reading the outside environment, measuring the water used in the home, recording changes in usage and environment and transmitting it to one of hundreds of nodes nearby.
They can be transferring this information by the day, the hour, even the minute.
With this new class of detailed information, water companies can plan strategies for customers to open their taps at the most optimal time, even offer incentives for them to conserve at certain hours. This can save customer’s money, reduce expenses for the water company, and preserve a precious resource for all of us.
To do it, you need a database that can handle the workload efficiently and with no problems.
The Right NoSQL Database to the Rescue
That’s where the RavenDB Enterprise NoSQL database comes in.
At the heart of your distributed database architecture, RavenDB can ingest millions of operations in real time, store it, aggregate it, and replicate it to a relational or nonrelational database along the data hierarchy.
If you have hundreds of nodes collecting data from all these IoT end points, connectivity becomes a real challenge. What happens when 10 or 15 of your edge point nodes aren’t able to connect to a regional server? Does the entire system collapse?
Not with RavenDB.
Your local nodes will continue to operate while offline, collecting and processing the data as instructed. Once connectivity is restored, the accumulated data will be pushed to the regional servers and the system will return to 100%. As a no-overhead NoSQL Database, you don’t have to waste additional developer time and resources. With RavenDB it all just works. Edge processing is a snap.
This enables you to get out of the Internet of Things what you are after: Better Data to respond to changing market conditions and be the first to seize new opportunities.
Mentioned in both Gartner and Forrester research, RavenDB is a pioneer in NoSQL database technology with over 2 million downloads and thousands of customers from Startups to Fortune 100 Large Enterprises.
RavenDB Features include:
- Easy to Use: RQL Query language is based on SQL
- Works well with existing relational database. ETL feature and migration to Document model available.
- Multiplatform: C#, Node.js, Java, Python, Ruby, Go
- Multisystem: Windows, Linux, Mac OS, Docker, Raspberry Pi
- Multi-model: Document, Key-Value, Graph, Counters, Attachments
- Works efficiently on older machines and smaller devices
- Built in Full-Text Search, MapReduce, and Storage Engine
- Schema Free
Grab RavenDB for free and get:
- 3 cores
- our state-of-the-art GUI interface
- Connectivity secured with TLS 1.2 and X.509 certificates
- 6 gigabyte RAM database with up to a 3-server cluster
- Easy compatibility with cloud solutions like AWS, Azure, and more
Woah, already finished? 🤯
If you found the article interesting, don’t miss a chance to try our database solution – totally for free!