Ask questions and see you at June, 7th, 8.PM. CEST: https://youtu.be/Uz1nLi5APVw
Also checkout recent episode:
Please keep the questions Jakarta EE-stic. Means: as short and as concise as only possible. Feel free to ask several, shorter questions. Upcoming airhacks.tv events are also going to be announced at meetup.com/airhacks
Hello Adam!
I was playing around with your BCE (front end edition) template and I have to admit - after the initial mindset change it is actually becoming quite intuitive!
One feedback item (or a question) - how would you implement something like JSON PATCH (RFC6902 - also described here) using your template? With redux capturing the history of changes in the background it would seem that there should be some way (or a hack) to transpose these actions into JSON PATCH as series of replace/add/etc. operations. Do you have any ideas? This could really help bridge the gap between "stateless REST" & "domain rich Gateway".
Seems most modern "public" API's (salesforce, OData-like, netsuite, paypal, JIRA, etc.) support PATCH in one way or another (albeit I see the MERGE (rfc7386) format more commonly). Curious to know - in your (mid-range enterprise projects/applications) - how do you typically see the update scenario handled for large, complex objects (e.g. work order with multiple line items, etc.)? Is it via PUT (i.e. idempotent, complete representation) or PATCH (i.e. just the delta)?