The Stack Overflow podcast is back! Listen to an interview with our new CEO.

New answers tagged

0

I would tend to agree in general with the idea that having two DBs is more trouble than it's worth but based on your situation, it's worth considering. One option you could also consider is gzipping the JSON. Depending on the size of the documents, this could save a significant amount of space. A nice thing about this is that you can set the MIME-type on ...


1

You need to implement horizontal scaling for your whole database, not just the JSON parts. Extracting the JSON parts will only buy you 70% more space once, so you will have the same problem again soon enough with the relational data. Since the JSON parts seem to be basically "black box" to your application you don't get a lot of benefit by storing it in a ...


1

Adding a second database isn't going to solve your problem. It will give you a whole bunch of new problems that you've identified, and likely more. What you need to do is structure your data better. Truly unstructured data is rare, most applications are a way to present data in a structured way, reflecting that structure correctly in a database can be ...


Top 50 recent answers are included