There is no such a thing as cross-service ViewModel Composition

Time was spent discussing ViewModel Composition concepts and their design. It's time for some code. Let's see Single Item Composition in action: how does the code look like?

ViewModels Lists composition has an interesting challenge: must be designed in such a way that it doesn't flood servers with tons of requests. Number of requests cannot exceed the number of services involved in the composition process, no matter how many items are composed. There is a light at the end of the tunnel (cit.)

ViewModel Composition can be scary, at a first look. The real world, we deal with every day, is complex as the information we manage are complex. Do we need to manually craft dedicated solutions or can we extract reusable patterns? There is always an exit to the maze.

Building distributed systems requires facing an interesting challenge: there is a dichotomy between the way behaviors and data are decomposed at the backend and the way users expect to consume them from the frontend. Services ViewModel Composition techniques are designed to help us overcoming this dichotomy.

I tried to-do lists many many times, and after a while I always failed. Being a procrastinator doesn't really help when it comes to to-do lists. Here is my reasoning on the root causes of the problem and how I decided to fix it.

I used to write 3 posts every week (on my Italian blog). Then she joined our lives and everything changed, from priorities to free time. Exactly a year later, so happy first birthday my love, I decided that it’s time to get back to that experiment.