This article gives you an overview of the architecture of Hashnode. The goal of this article is to give you a broad architecture of our involved services. Overall Architecture This is our overall architecture. A request starts on the user's side. It...
engineering.hashnode.com7 min read
thank you very much
Great stuff. Easily understandable. Can you also share how hashnode built the Rix?
Would really love it if you could explain the event-driven architecture and the services used to make it possible in a separate article.
Nice article btw
Great article! Can you elaborate more on how you document event types, producers and consumers to make the overall architecture scalable, discoverable and maintainable?
This was an amazing read, how real life architecture is implemented. Thanks
A great explanation in a concise and structured format. Though many things went over my head, I will surely look upon them to make them clear. Great Writing! βοΈ π.
Wow. Thank you for this information, I get to see real-life architecture. A lot of stuff went over my head. I find it interesting that it is possible to interact with Vercel API to assign custom domains. That's something on my list.
Quick question, I was expecting to see anything about using a cron job, but didn't so does it mean Hashnode don't use it? Or is it part of the background process?
Really cool. Appreciate the look-see
Berker Tasoluk
great