Engineering on Birdor Blog

A Minimal Service Framework That Returns to the Essence of Go

Sun, 28 Dec 2025 00:28:00 +0800

Preface: Why Build Yet Another Go Framework

In today’s highly mature Go ecosystem, “building yet another Go web framework” may seem redundant—or even boring.

We already have:

Feature-rich, full-stack frameworks with massive communities
Performance-oriented, low-level HTTP / RPC frameworks
Cloud-native application runtimes deeply integrated with Kubernetes
Complete engineering systems tailored for microservices

Plumego is not meant to compete with them.

The motivation behind Plumego comes from a different, often overlooked, set of real-world engineering needs:

Plumego vs Common Go Frameworks: Design Trade-offs Explained

Sun, 28 Dec 2025 00:36:00 +0800

Introduction: Comparing Frameworks Is Ultimately About Values

In technical communities, discussions of “Framework A vs Framework B” never seem to end.

But experienced engineers usually understand one thing clearly:

Framework debates are rarely about right or wrong technology—they are about value trade-offs.

Plumego was not created in a “blank market.”
On the contrary, it deliberately chose a seemingly “unattractive” path in an already thriving Go ecosystem.

Therefore, this article does not attempt to prove that:

When You Should Not Use Plumego

Sun, 28 Dec 2025 07:30:00 +0800

Introduction: A Responsible Framework Must Define Its “Non-Use Cases”

Any framework that takes engineering quality seriously must be willing to answer one question:

“In what situations should you not use me?”

If a framework claims that it:

fits every team,
fits every stage,
fits every business,

then it is almost certainly not credible.

Plumego was never designed to be a universal answer.
It is a choice explicitly created for a specific class of engineering problems.

Plumego Advanced Guide: Designing Explicit, Scalable Go Services

Tue, 30 Dec 2025 20:30:00 +0800

Plumego Advanced Guide: Designing Explicit, Scalable Go Services

Introduction: Beyond the Basics

The introductory Plumego documentation explains what Plumego is and why it exists. This guide focuses on a different question:

How do you design serious, long-lived systems with Plumego?

This article assumes that you already understand:

Go fundamentals
HTTP server basics
The core Plumego APIs
The philosophy of explicitness

What follows is an advanced, production-oriented tutorial. We will explore architectural patterns, not just APIs. The emphasis is on design decisions, trade-offs, and operational correctness—the areas where Plumego provides leverage without hiding complexity.

Plumego: A Deliberate Go Framework for Engineers Who Value Explicitness

Tue, 30 Dec 2025 19:00:00 +0800

Introduction: Why Another Go Framework?

The Go ecosystem does not suffer from a lack of web frameworks. From minimalist routers to batteries-included solutions, developers can choose from a wide spectrum of abstractions. Yet, despite this abundance, many experienced teams eventually encounter a recurring problem:

Their framework either does too little to guide large systems, or too much to stay out of the way.

Plumego exists in the narrow but important space between these extremes.