What Is Unique About Waku

Hi,

Waku v0.22 has been released. It’s a great milestone on the path toward the v1 alpha. Today, I’d like to share one of my thoughts from the journey of developing Waku.

So—what makes Waku unique?

Previously, I shared my original motivation for building Waku.

As a library developer, I wanted a framework I could build libraries on top of. As a framework developer, the key question became: What belongs to the framework core, and what should be part of external libraries?

One of the main challenges is making Waku’s router a library—not a core part of the framework. Currently, the router API is built using Waku’s minimal API. The minimal API is tightly coupled with the framework core, while the router API is only indirectly coupled. As the router requirements grow, maintaining this separation gets harder—but I’m committed to keeping this architecture.

Technically speaking, Waku is a router-agnostic framework, and Waku’s router is just a library. This means you could build an entirely different router library and use it in place of the default one.

I’m really looking forward to seeing alternative router libraries come out. That would be the ultimate proof that Waku’s architecture is truly router-agnostic.

Happy coding.