☒ In this example, it is persisting the data into memory for the life of the request. If there are a bunch of concurrent streams, then this could be problematic. However, on the 2GB RAM servers that I'm running Drifting Ruby on, I haven't seen it become a real issue yet.