Cloud Native Development Patterns and Best Practices

Example – Author BFF

In Chapter 2, The Anatomy of Cloud Native Systems, we discussed how the data life cycle is a useful strategy for decomposing a system into bounded isolated components. As the data in the system ages, its storage requirements will change and thus the component that owns the storage changes as well. The users who interact with the data will also change over the data life cycle and thus so do the frontend applications used over the data life cycle. In a reactive, cloud-native system, a great deal of data is automatically created as events flow through the system. However, an event chain has to start somewhere. If it doesn't start in an external system, then it starts when a user creates it. This is where the Author user ...