---
title: "Comment by Michael Mwambyale on \"How I got introduced to event-driven architectural design.\" | Hashnode"
description: "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"
url: "https://hashnode.com/posts/how-i-got-introduced-to-event-driven-architectural-design/6a7f280510ab3701b4953005/comment/6a902eb8c19b280a0b5ef752"
---

[Discussion](https://hashnode.com/posts/how-i-got-introduced-to-event-driven-architectural-design/6a7f280510ab3701b4953005)

Comment [How I got introduced to event-driven architectural design.](https://hashnode.com/posts/how-i-got-introduced-to-event-driven-architectural-design/6a7f280510ab3701b4953005)

[Michael Mwambyale](https://hashnode.com/@cybermichael)

[Aug 27](https://hashnode.com/posts/how-i-got-introduced-to-event-driven-architectural-design/6a7f280510ab3701b4953005/comment/6a902eb8c19b280a0b5ef752)

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.

[Chisomo Chiweza](https://hashnode.com/@mwprogrammer)

[Aug 28](https://hashnode.com/posts/how-i-got-introduced-to-event-driven-architectural-design/6a7f280510ab3701b4953005/comment/6a902eb8c19b280a0b5ef752#reply-6a91e5363949f452be29bffb)

Thank you so much for your kind words! I had a lecturer who used to say programming is both an art and a science - emphasis on 'art'.