Tyk vs Apigee Flexible and Scalable architecture However, there is plenty there to get you and your team started. As of this writing, he is still working to complete the book. More Info: Check out Brandolini’s book on LeanPub. Often, event storming is a great way to find boundaries where there are clear areas of concern that demand an API and perhaps two or more microservices. I’ve seen this technique used to gain a breadth-wise understanding of how processes work across a company, as well as to further deep-dive into a specific area. Usefulness: This technique is best used when you have a product or area of the business that needs to be understood better. They often referred back to the board often whenever a question arose, to determine what was previously discussed and how newly-gained information might impact their previous decisions and assumptions. The group used the process throughout their design effort, to identify bounded areas that could be realized through internal systems, off-the-shelf solutions, and highly-cohesive APIs. Most importantly, teams identify hotspots where things are unknown and need further research or decisions to be made.Įxample: Below is a photo of the early stages of an event storming session that I facilitated:
The board is then expanded to include read models, external systems, policies, commands, and UI components. user intentions), system events, external systems, or simply the passage of time. Then, the group asks what caused each event to happen. Once all events have been identified, you should be able to walk the events from the beginning to ensure you haven’t missed anything, reorganizing the positions of the events as you go. This means asking questions such as “What happened before that?”, e.g. Then, work along the process to identify other surrounding events. When identifying the initial set of events, it is beneficial to start near the end of the process. The process begins by capturing the domain events that occur, e.g. All work is done using sticky notes on a large surface area. The process isn’t meant to drive brainstorming, but rather create a shared understanding of how one or more systems work in cooperation to solve everyday problems. It requires that subject matter experts, developers, and other roles work together. Overview: Event Storming is a technique developed by Alberto Brandolini to drive analysis and understanding of a problem domain. Let’s examine five techniques that can help you validate your API and service designs before, during, and after the design process.
API SEQUENCE DIAGRAM EXAMPLE CODE
Just as we use test-driven development to turn requirements into test cases that we code against, these design techniques help us to design APIs and microservices that meet the needs of our stakeholders. One way of validating your API and microservice designs is to use some design techniques to surface issues before we commit to our design. So, how can we avoid designing an API that doesn’t meet the needs of our consumers? Too often, our initial assumptions about our API and microservice designs are incorrect as they encounter the real world.
0 kommentar(er)
