---
title: "Comment by Andrea Diotallevi on \"Hashnode's Overall Architecture\" | Hashnode"
description: "Great article! Can you elaborate more on how you document event types, producers and consumers to make the overall architecture scalable, discoverable and maint"
url: "https://hashnode.com/posts/hashnodes-overall-architecture/6524d6300881118bc31970bc/comment/652a3f81d2fa06034fe35a42"
---

[Discussion](https://hashnode.com/posts/hashnodes-overall-architecture/6524d6300881118bc31970bc)

Comment [Hashnode's Overall Architecture](https://hashnode.com/posts/hashnodes-overall-architecture/6524d6300881118bc31970bc)

[Andrea Diotallevi](https://hashnode.com/@AndreaDiotallevi)

[Oct 14, 2023](https://hashnode.com/posts/hashnodes-overall-architecture/6524d6300881118bc31970bc/comment/652a3f81d2fa06034fe35a42)

Great article! Can you elaborate more on how you document event types, producers and consumers to make the overall architecture scalable, discoverable and maintainable?

[Sandro Volpicella](https://hashnode.com/@SandroVolpicella)

[Oct 16, 2023](https://hashnode.com/posts/hashnodes-overall-architecture/6524d6300881118bc31970bc/comment/652a3f81d2fa06034fe35a42#reply-652cf476a377d91a4aa26db3)

Thanks!

-   event types: We have an own package in our monorepo where we defined all event types and ZOD schemas
-   consumers: We follow the EventBridge subscription pattern. Each consumer owns the rule. So we don't really document something here. Each consumer can decide which ones to use
-   producers: The main producer is our GQL API. We have abstracted event emitters for actions like post publish, update, etc.
