Evolution of business logic from monoliths through microservices, to functions
adrian cockcroft

I would further decompose value into outcomes. To paraphrase Steve Jobs, people don’t buy products, they buy better outcomes for themselves, value is too amorphous and outcomes can be aligned to microservices more effectively. Whether it is getting a taxi more reliably, or booking a cool pad in a place you have never been to, we are all seeking what we percieve as better outcomes. Outcomes also moves the discussion outside the “digital” realm, “digital xyz” being just a more efficient way to reach a particular outcome.

On the microservices side, I would suggest adding a section on “consistency” (the eventual kind), not to mention the (re)use of microservices in different activities, the activities you perform to reach a particular outcome.

When you look carefully, you’ll see that most companies focus on helping their customer reach 3–4 outcomes (Amazon: find, purchase, deliver products, Netflix: find, subscribe, view, Kodak: Take, Develop, Print — though they missed the most important outcome people want to reach when they take a picture, share it, yes, they could have been Facebook, if only they had looked at the outcomes people want to reach, but I degress). Beyond that there is a myriad of small back-office outcomes (such as returns, refunds and what not) that you still need to take into account and that’s where consistency and activity based consumption of microservices become important. I am not fully certain “lambda” alone would take care of this (not so) complex world.

We are clearly heading in the right direction and I am a big Lambda proponent, but we must keep an eye on the macro/big picture as well.