Introducing Plumego — A Standard-Library-First Go HTTP Toolkit
Plumego is a small, explicit, standard-library-first Go HTTP toolkit designed for maintainable services, ordinary net/http compatibility, and agent-friendly engineering workflows.
tag
Plumego is a small, explicit, standard-library-first Go HTTP toolkit designed for maintainable services, ordinary net/http compatibility, and agent-friendly engineering workflows.
A deep engineering essay on the philosophy behind Plumego. This article explores why explicit systems outperform implicit ones in long-lived software, how hidden abstractions accumulate technical debt, and why Plumego is intentionally designed as a framework that forces clarity, ownership, and architectural responsibility.
A deep, end-to-end walkthrough of building a real-world backend service with Plumego. This article traces a request from HTTP entry, through routing, middleware, context, use cases, domain logic, and infrastructure, explaining architectural decisions and trade-offs along the way.
A comprehensive, in-depth decision guide for evaluating Plumego as a Go framework. This article examines architectural trade-offs, team maturity, system lifecycle, operational concerns, and long-term maintainability to help serious Go teams decide when Plumego is the right choice.
An advanced, in-depth guide to Plumego. This tutorial explores real-world architecture patterns, middleware composition, context design, lifecycle management, observability, and building production-grade Go services with Plumego.
Plumego is a deliberate, explicit Go framework designed for long-lived services, disciplined teams, and engineers who value clarity over magic. This article provides a comprehensive introduction to Plumego’s philosophy, architecture, and practical usage.
Plumego is not for every project. This article explains, from the perspectives of project stage, team structure, business goals, and risk models, when you should not choose Plumego.
A comparison between Plumego and mainstream Go frameworks from the perspectives of design philosophy, engineering boundaries, dependency strategy, and long-term maintenance cost—explaining why they differ and which types of projects they best suit.
Plumego is a minimal, composable, and highly controllable service framework built on the Go standard library, designed for long-term maintenance, low dependency, and engineering consistency.
A practical, Birdor-style comparison of Python, Go, and Rust — strengths, weaknesses, performance, concurrency, ecosystems, and when to choose each.
Go’s net/http package is fantastic—but sometimes you want to see what’s really happening under the hood. In this article, we’ll build a tiny HTTP/1.1 …
Go’s net/http package is deceptively simple on the surface—just call http.ListenAndServe() and pass a handler. But beneath its minimal API lies a …
High-performance networking is one of Go’s strengths. With lightweight goroutines, a rich net package, and strong concurrency primitives, Go is a …
The net package is the foundation of all network programming in Go. Everything — from HTTP servers to gRPC, Redis clients, DNS resolvers, and …
Go’s context package is one of the most important tools for building robust, cancellable, timeout-aware, concurrent programs. Whether you are writing …
Go (often called Golang) is a modern programming language designed at Google. It focuses on simplicity, performance, and built-in concurrency. If you …