I am used to seeing data in tables and their relationship via foreign keys. I would like to move on to noSQL (key-value) store. A challenge to me is how to stop thinking about foreign keys and tables and think everything in a single key-value store. Does anyone point to guide/links how to move away from RDBMS mindset to key-value store mindset. Real life examples of moving rdbms schemas to noSQL would be great.
Ask HN: How does a RDBMS developer migrate to noSQL ?
1–5 of 5 posts
Re: Ask HN: How does a RDBMS developer migrate to noSQL ?
#2Why do you want to move to a KV store? Don't just move for the sake of it. If you have a real problem that requires a KV store then sure, but it sounds like you're just doing it cause everyone else is. Don't optimise for a problem you don't have (yet).
Re: Ask HN: How does a RDBMS developer migrate to noSQL ?
#3You may check this presentation from MIX10 "Using Storage in the Windows Azure Platform" http://live.visitmix.com/MIX10/Sessions/EX11
Re: Ask HN: How does a RDBMS developer migrate to noSQL ?
#4I dont understand the constant desire to replace the relational model. It works great to store most types of data in it, and its very flexible to do ad hoc reports if you have a good understanding of SQL.
I ❤ ORDER BY, GROUP BY, DISTINCT, SUM(), COUNT(1) etc ducks
Re: Ask HN: How does a RDBMS developer migrate to noSQL ?
#5You know that table where you just have an id and a blob or text field? Start with that.