4dotnet pizza session: When events occur
Most developers like to build microservices over monoliths; we want to believe that makes things easier—our teams working autonomously on small systems that are easier to reason about. We tend to overshadow the additional costs, complexity, organizational change, and knowledge required to operate a network of those interconnected (micro)services.
Let alone the scary fact that we now need to reason based upon data that is eventually consistent. In this session, we will look at how to start thinking asynchronously about your system/services.
What can we do to store that flow of events that occur, and what additional value does that bring us. How can we feel safe again about being eventually consistent?
https://twitter.com/Jan_de_V/status/1392539073508777988
Most developers like to build microservices over monoliths; we want to believe that makes things easier—our teams working autonomously on small systems that are easier to reason about. We tend to overshadow the additional costs, complexity, organizational change, and knowledge required to operate a network of those interconnected (micro)services.
Let alone the scary fact that we now need to reason based upon data that is eventually consistent. In this session, we will look at how to start thinking asynchronously about your system/services.
What can we do to store that flow of events that occur, and what additional value does that bring us. How can we feel safe again about being eventually consistent?
https://twitter.com/Jan_de_V/status/1392539073508777988