Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

The Impact of IoE on NoSQL

DZone's Guide to

The Impact of IoE on NoSQL

· IoT Zone
Free Resource

I believe the Internet of Everything will read and write to NoSQL databases.

There was a great article on MQTT and CoAP in Eclipse's February newsletter.

  • The IoE will read and write to NoSQL databases.
  • The IoE will communicate over MQTT / CoAP.

What's the problem? NoSQL databases do not communicate over MQTT / CoAP.

That may need to change that. However, it is not a problem. It's a symptom.

Why is the database always the last stop?

Write #1

  1. Send data to the application server and / or service bus.
  2. Send data to the database.

Write #2

  1. Send data to the application server and / or service bus.
  2. Send data to the message broker.
  3. Process the data as a stream.
  4. Send processed data to the database.

The database is the last stop.

What if the database was the first and last stop?

  1. Send data to the database via a message broker.
  2. Process data as a stream or via services.
  3. Send processed data to the database.

Summary

There is a place for application servers, and a database first architecture may not be practical for every application. However, I believe it may be practical for machines and things. It may be practical for simple writes at high throughput. It may be practical for sensor data.

I tend to think of traditional databases as being data at rest. I tend to think of stream processors as being data in motion. Perhaps the next generation of databases will be data at rest and data in motion.

Topics:

Published at DZone with permission of Shane Johnson, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

SEE AN EXAMPLE
Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.
Subscribe

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}