normalizr

I am having a hard time structure my data in a localized blogging app. My app is displaying posts, with embedded pictures (one-to-many), in three languages (English, French and Russian). The visitor can choose its locale. The editors can edit the localized versions of their posts in the three languages. For the moment, the structure of my store looks like this: { articles: { en: { 1: { id: 1, title: "my first title", body: "my first body", picture_ids: [1, 2, 3]}, 2: { id: 2, title: "my second title", body: "my second body", picture_ids: [1, 4, 5]}, 3: { id: 3, title: "my third title", body:

I'm using ReactJs with Redux and on some tutorials and codes I see people suggesting and using normalizr to keep the state flat . But what is the real advantage in keeping it flat ? Will I encounter any problems if I don't ? Is it necessary ? Three main reasons: Updating nested Javascript objects immutably generally results in uglier code that is harder to maintain, unless you use a utility library to wrap up the process Immutably updating nested data requires that you return new copies of all items in the nesting hierarchy. Since components generally do shallow-equality reference comparisons

Looking the examples from the README : Given the "bad" structure: [{ id: 1, title: 'Some Article', author: { id: 1, name: 'Dan' } }, { id: 2, title: 'Other Article', author: { id: 1, name: 'Dan' } }] It's extremely easy to add a new object. All I have to do is something like return { ...state, myNewObject } In the reducer. Now given the structure of the "good" tree, I have no idea how I should approach it. { result: [1, 2], entities: { articles: { 1: { id: 1, title: 'Some Article', author: 1 }, 2: { id: 2, title: 'Other Article', author: 1 } }, users: { 1: { id: 1, name: 'Dan' } } } } Every