DEV Community

Discussion on: Is a Redis ORM a Horrible Idea?

dbanty profile image
Dylan Anthony Author

Oops, I clearly made a mistake in describing the issue! I clarified a bit above. When we were trying to use MySQL for this, the data was not JSON. You do bring up a good point though in that we don't need the power of a relational database (e.g. joins) for this sort of data. I have been looking at DynamoDB to see if that will give us what we need. Though maybe Mongo would have better tooling.

brandinchiu profile image
Brandin Chiu

Reading over some of your other comments implies that it's only a subset of your data that has this problem, not the entire dataset.

In that case, mixing storage engines is probably the preferred solution. If this "transient data" is short-lived between periods of long persistence, then redis makes a lot of sense.