Timeline for REST API: Handle "partial" nested objects
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 2, 2021 at 15:00 | history | tweeted | twitter.com/StackSoftEng/status/1366765283688513540 | ||
| Aug 9, 2016 at 7:31 | vote | accept | Michael Marvick | ||
| Aug 8, 2016 at 10:11 | comment | added | guillaume31 | @MichaelMarvick I think Luc Franken has a brilliant answer below. For a good way of organizing your backend architecture, you can have a look at CQRS. It suits that idea of "denormalizing" pretty well. | |
| Aug 8, 2016 at 9:31 | answer | added | Luc Franken | timeline score: 11 | |
| Aug 7, 2016 at 21:51 | comment | added | Michael Marvick | @DavidPacker I think you're right here. I think there may be ways to communicate the data over the API that will make architecting a solution easier. But in the end, figuring out how to deal with storing and updating "partial" objects coming over the wire in a way that minimizes data inconsistency is the goal. | |
| Aug 7, 2016 at 21:40 | comment | added | Andy | Your problem has less to do with REST than it has with your actual application architecture. | |
| Aug 7, 2016 at 21:39 | review | First posts | |||
| Aug 14, 2016 at 21:23 | |||||
| Aug 7, 2016 at 21:36 | history | asked | Michael Marvick | CC BY-SA 3.0 |