You can have a design where your previous version of a record gets automatically copied into another table along with the timestamp of the operation. Then you can slice this history however you want. All with no additional app code.

But I wouldn't write off the noDB approach for various transitional data, or data that isn't mean to live long anyway, like tweets.