My application uses a relational database but there is a feature requirement to display a survey form to users at the end of each quarter/year etc. I understand that this data maybe used to do some analysis in near future but the issue is the form would have many key value pairs and I am sure that it will keep on changing.
I did some research and found that people suggest to have NoSQL databases for these kind of stuff but I can't change my database for just one feature, other option is to have a
JSON column in the database table and store all the key-value pairs there.
I don't have enough experience to know what can be tradeoff or if there are other alternatives?