If you are a software engineer, you have probably spent countless hours staring at architecture diagrams. We use them for everything: designing new microservices, documenting legacy systems, and onboarding new team members.

We boot up tools like Draw.io, Lucidchart, or Excalidraw, meticulously dragging boxes, drawing arrows, and color-coding databases. And when we are done, we export a shiny, static .png file.

But there is a fundamental problem: Software is dynamic; our diagrams are static.

A static image cannot adequately describe the complexities of modern, event-driven, distributed systems. It doesn’t tell you when a message is placed on a queue, how long a database lock holds up a thread, or the difference between a blocking synchronous HTTP call and a non-blocking asynchronous event.

I wanted a tool where I could not just draw an architecture, but simulate it. When I couldn’t find exactly what I was looking for, I decided to build it.
https://bishoku.github.io/yada/

We boot up tools like Draw.io, Lucidchart, or Excalidraw, meticulously dragging boxes, drawing arrows, and color-coding databases. And when we are done, we export a shiny, static .png file.

But there is a fundamental problem: Software is dynamic; our diagrams are static.

I wanted a tool where I could not just draw an architecture, but simulate it. When I couldn’t find exactly what I was looking for, I decided to build it.
https://bishoku.github.io/yada/

YADA

Draw the system, Explain the flow.

Draw the system, Explain the flow.