Ho do you patch your JSON in your projects about json-patch

[tomalec]

Personally I do not have wide experience with other server-side / database engines for JSON Patch.
I use Starcounter - besides out of the box JSON-Patch support it serves great performance and together with PuppetJS makes creating single-page MVC app very simple. You can create JSON models just by writing an example .
Here you have an example of the smallest app with this stack: https://github.com/Starcounter/Squared

Maybe @Starcounter-Jack, or @warpech could elaborate more on that.

[warpech]

I think that in the long term we should see support for JSON-Patch in database drivers. That would reduce greatly the code overhead.

I guess that so far you need to use some server side implementation of JSON-Patch (see GitHub searches for JSON-Patch and RFC 6902) or just parse it as JSON and loop through the incoming patches, while interpreting the input patch-by-patch.

Last year, I have written some server side controllers that loop through incoming patch and respond in a patch (keep in mind they are quite naive and rusty by now):

• Node.JS - https://github.com/PuppetJs/PuppeteerJs/blob/master/examples/basic/app.js
• PHP - https://github.com/warpech/angular-patch/blob/3ab013b49068c250de5e5d9d7c218204fab2c4d9/examples/php/controller.php

In future, we want to work on server side implementations of PuppetJS in more languages, which will greatly improve the programming experience of using JSON-Patch. See the doc: https://github.com/PuppetJs/PuppetJs/wiki/Server-communication

[skotchio]

Thanks for the answers guys and good luck you with working on JSON+Patch. I have the following idea in storing JSONPatch and want to share with you:

Each big JSON document stored as bundle of patches and get compiled when fetching by user. What do you think about this approach?

[warpech]

I think this is a good solution if your JSON tree represents a single document.

In my case, the JSON tree represents the application view-model (that is: current state of the application including fragments of various documents) so I need to parse incoming patches on server and apply changes in many places.

[skotchio]

@warpech yes if you have to apply patches in many places then my approach is not useful for you. And you're right, my JSON tree represents a single document. Also I want to implement "revision history" feature but can't find good practices around using of Redis. Basically I don't understand which of the Redis data structure type should I use for my purpose.

Could you advise something?

[warpech]

Closing as answered. I know I haven't answered the last question, but that is quite out of scope of this library.