Architecting UIs for Change

From the UI side of things we’ll need a search page, an item detail page, a cart page, and a checkout page. Now, we have to share some piece application logic for fetching and retrieving the shopping cart data in a way that can be used by the cart team, but also can be used by every other team. The three predominant approaches we’ve seen to building stateful UIs on the Web in the last decade have essentially been:

Option #1 is the embodiment of the first part of the shopping cart example I mentioned above.

Source: joreteg.com