Home/ Questions/Q 1008923
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-16T08:50:49+00:00

I thought this was a n00b thing to do. And, so, I’ve never done

  • 0

I thought this was a n00b thing to do. And, so, I’ve never done it. Then I saw that FriendFeed did this and actually made their DB scale better and decreased latency. I’m curious if I should do this. And, if so, what’s the right way to do it?

Basically, what’s a good place to learn how to store everything in MySQL as a CouchDB sort of DB? Storing everything as JSON seems like it’d be easier and quicker (not to build, less latency).

Also, is it easy to edit, delete, etc., things stored as JSON on the DB?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    CouchDB and MySQL are two very different beasts. JSON is the native way to store stuff in CouchDB. In MySQL, the best you could do is store JSON data as text in a single field. This would entirely defeat the purpose of storing it in an RDBMS and would greatly complicate every database transaction.

    Don’t.

    Having said that, FriendFeed seemed to use an extremely custom schema on top of MySQL. It really depends on what exactly you want to store, there’s hardly one definite answer on how to abuse a database system so it makes sense for you. Given that the article is very old and their main reason against Mongo and Couch was immaturity, I’d re-evaluate these two if MySQL doesn’t cut it for you. They should have grown a lot by now.

    • 0