Skip to content

andresrinivasan/redisedge-patterns

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

12 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

RedisEdge Patterns

For IoT/Edge, use patterns have emerged around data ingress, processing, event detection, data egress. The intent here is to share example(s) of those patterns

Data Ingress

We usually use one or Streams for ingress. This makes it easier to connect the data to other data structures via a Gear. See Anti Patterns for additional scenarios.

Data Orchestration

RedisGears registers for events (new data) on Streams and then takes appropriate action. This could be something entirely covered by the Gear or it could be a handoff to another data structure.

IFTTT

Techncially you can do anything in a Gear that you can do in Python. But do you really want to write all those conditions. Something like JSONLogic makes an excellent engine for this kind of business logic.

Anti Patterns

  1. If all the data is time series, RedisTimeSeries effectively acts as a data/sample stream. Of course a Gear can't react to it directly though data traditional Redis events can be used as triggers or the app can invoke a Gear. Typically the app is interacting directly with one or more time series.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published