Really enjoyed reading this, especially the part about the distributed monolith. It’s easy to get carried away with breaking systems into services without first asking whether the problem actually needs it.
I also liked the way you explained how you arrived at event driven architecture through a real problem rather than just adopting the pattern because it’s popular. The example of letting the file processing continue even after the user logs out really brings the value of asynchronous processing to life.
Good read. The reminder that architecture is about trade offs and context is something a lot of developers can easily overlook.
Really enjoyed reading this, especially the part about the distributed monolith. It’s easy to get carried away with breaking systems into services without first asking whether the problem actually needs it.
I also liked the way you explained how you arrived at event driven architecture through a real problem rather than just adopting the pattern because it’s popular. The example of letting the file processing continue even after the user logs out really brings the value of asynchronous processing to life.
Good read. The reminder that architecture is about trade offs and context is something a lot of developers can easily overlook.