These are chat archives for
Sign in to start talking
Low Latency Storage
Jun 15 2015 17:32
For this to be more useful you need to have multiple streams persisted in one jouranl
Say I have 30 items I have to journal putting them into different journals may not make sense and perhaps may not be efficient
Jun 15 2015 17:41
Also you can have a stream abstraction for writing values
Queries can be on the streams
The streams can have an identifier and would be analogous to tables in a normal DB
Jun 15 2015 17:52
Also have a look at:
Jun 15 2015 18:03
Also stream composition (like multi table joins - Fan In, Fan Out patters) must be well thought thought.
Perhaps compositional streams analogous to views in normal SQL
Your thoughts on this?