> you can submit (POST) JSON records on the channel. The channel acts as an FIFO array of fixed length, allowing you to keep track of record history. [...] If a

> you can submit (POST) JSON records on the channel. The channel acts as an FIFO array of fixed length, allowing you to keep track of record history. [...] If a channel is full, posting a new record will automatically push out the oldest one. sample plan is $4.5 / month, 50 channels, 50 records per channel, 50 kB record size limit -> 120MB of data. There is no stated limit on # of requests, but I am sure one would appear if you make enough of them. This seems like a very specific primitive rather than a general purpose system I can imagine a use case for this, but it seems pretty contrived. I cannot imagine why one would choose this vs some existing nosql db, which is infinitely more flexible, substantially cheaper, and much less likely to disappear.