About gland

[m-mdy-m]

I'm working on a deep-dive article about Gland — covering everything from its name and philosophy to its architecture, broker system, design patterns, and real-world usage.

Since the official documentation is still a work in progress, I want this article to help clarify things and answer common questions.

If you've ever felt confused or had questions while using or exploring Gland, let me know — I'd love to include your questions in the article and make it as helpful as possible!

[DPirate]

Hello, what problems or inefficiencies of node.js are you addressing here and how?

[m-mdy-m]

I'm not trying to fix Node.js inefficiencies in a general sense or argue that the DI systems in frameworks like NestJS are problematic—they work great in many contexts. Instead, gland is designed as a lean, pure event-driven system that minimizes dependencies and shifts the focus entirely onto events as the primary communication mechanism.

By cutting down on pervasive DI and embracing EDS patterns, gland offers a simpler, more decoupled architecture that is naturally aligned with asynchronous operations. This approach streamlines inter-module communication, making the system more flexible and scalable, especially in scenarios like microservices and event-sourced applications.

In short, gland isn’t about fixing Node.js shortcomings—it’s about presenting an alternative architecture that emphasizes minimalism, decoupling, and natural event flows.