As someone who deals with sensor data, the tricky part is really not the write-rate, but rather dealing with messy data. There&#x27;s a lot of parallelism in sensor network streams, and for many domains you never look at the sensors from one device against the sensors of another device, so you can put them in entirely different databases and it doesn&#x27;t matter. (It&#x27;s not true in every case, of course, but if you&#x27;re doing time series&#x2F;streaming, ask yourself if it&#x27;s true for you before picking a system)<p>The real pain is handling data that arrives out of order or otherwise very late, or handling data that never arrives at all, or handling data that&#x27;s clearly wrong. Worse, you may have streams that are defined&#x2F;calculated from other streams for some algebra on series, e.g. series C is series A plus series B - so handling new data on A means you need to recalculate&#x2F;update the view for C.<p>Oh, and you&#x27;d like this all to be mostly declarative so you have some way to migrate between systems if you need to switch for whatever reason.<p>Apache Beam&#x2F;Google Dataflow gets a lot of this stuff right: it&#x27;s not quite as declarative as I&#x27;d like but it gets the windowing flexibility right and handles restatements at a data model level.