Summary of All our aggregates are wrong - Mauro Servienti

00:00:00 - 00:55:00

In this video, Mauro Servienti discusses the problems with aggregating data across different services, and how to solve them using a view model composition. The video also provides a diagram of the process.

• 00:00:00 Mauro Servienti explains that because he works remotely, he rents an office space a few kilometers away from his home. He bikes there, and his favorite snacks are bananas. One day, while biking to work, he experienced a failure with his snacks--his banana was dead. He realized that an aggregate could be designed to solve this problem, and he applied business requirements to create an aggregated data and behaviors system for his Amazon product.
• 00:05:00 This YouTube video discusses how e-commerce websites need to change their shopping cart structure in order to handle price changes and inventory changes. This is problematic because it creates congestion and contention over a single resource.
• 00:10:00 The video discusses how coupling among various parts of an application can lead to problems. It argues that we should try to break down the shopping cart concept into smaller, more manageable pieces. This would allow for easier communication, coordination, and management.
• 00:15:00 The video discusses the need for quantity in order to understand how many items are living in shopping carts, how shipping and marketing differ in their needs, and how the shopping cart concept can be owned by sales. It concludes by saying that this approach is sufficient from a technical perspective, but that it creates additional problems when information is split into multiple contexts.
• 00:20:00 Mauro Servienti discusses the problem of aggregates in systems, which can lead to coupling and responsibility problems. He discusses how using a cache can resolve these issues.
• 00:25:00 This YouTube video discusses the challenges of aggregating data across different services, and how to solve them using a view model composition. The video also provides a diagram of the process.
• 00:30:00 Mauro Servienti discusses how the code for a product page could be laid out, and how decomposing the view model into individual services allows for more consistent updates across multiple services. He also discusses how post requests containing just the product ID and quantity would update the system in a consistent state.
• 00:35:00 This video discusses how an application's various aggregates (such as those for shopping, shipping, and orders) should be able to communicate with each other in order to work properly. The author demonstrates how this can be achieved using a code example, and explains how failures can be handled. The example uses a queue to delegate the handling of failed requests to the back-end.
• 00:40:00 Servienti discusses the problems with having tight coupling between different parts of an application, and how using full vertical slices can help to alleviate these problems.
• 00:45:00 Mauro Servienti discusses the importance of behavior over data in microservice architectures, and how designing for behavior allows for easier communication between services. He also points out that data can be removed from the design if it is not important to the behavior being modeled.
• 00:50:00 In this video, Mauro Servienti discusses how we can improve our business processes by considering the boundaries between services and how to design user interfaces that are easy to understand. He also discusses how bandura's are key to success, and how UX designers play a crucial role in helping to translate business concepts into user interfaces.
• 00:55:00 In this video, Mauro Servienti discusses how businesses can avoid making mistakes when creating their product names and pricing. He also discusses how to keep data related to customer status together. Finally, he discusses how to use composition techniques to bring everything back together in the user interface.