FAQ

This section answers frequently asked questions about Plumego.

Not beginner questions.
Not marketing questions.
But real questions that arise once you have read the docs
and started building real systems.

If you find yourself thinking:

• “Why doesn’t Plumego do X?”
• “Is Plumego suitable for Y?”
• “Am I using Plumego the right way here?”
• “How does Plumego compare to other frameworks?”

You are likely in the right place.

What This Section Is For

The FAQ exists to:

• Clarify design intent
• Address common misunderstandings
• Explain trade-offs explicitly
• Save you from reading the entire documentation again

Each answer is intentionally concise,
and points you to deeper documentation when needed.

What This Section Is Not

The FAQ is not:

• A replacement for the docs
• A shortcut to understanding Plumego
• A list of feature requests
• A support forum

If a question requires deep explanation,
it belongs in Concepts, Architecture, or Guides — not here.

Typical Topics Covered

Questions in this section typically involve:

• Design philosophy and constraints
• Comparisons with other Go frameworks
• Performance expectations
• Suitability for different project sizes
• What Plumego intentionally does not provide
• When Plumego may not be the right choice

The goal is alignment, not persuasion.

How to Use the FAQ

Recommended reading strategy:

1. Read the docs normally
2. Build something non-trivial
3. Come back here when friction appears

If the FAQ answers your question,
it will usually link to a more detailed page.

About the Tone of Answers

FAQ answers are:

• Direct
• Honest
• Sometimes opinionated
• Always consistent with design principles

If an answer feels restrictive,
that restriction is almost certainly intentional.

Scope and Evolution

The FAQ evolves slowly.

New questions are added only when:

• The same question appears repeatedly
• The misunderstanding is reasonable
• The answer clarifies an important boundary

This keeps the section focused and useful.

Relationship to Other Sections

• Roadmap explains long-term direction
• Non-Goals explains explicit refusals
• Design Principles explain constraints
• When Not to Use Plumego explains limits

FAQ connects these ideas to concrete questions.

Example Questions You’ll Find Here

• Why doesn’t Plumego include a DI container?
• Is Plumego suitable for microservices?
• How does Plumego compare to Gin / Echo / Fiber?
• Is Plumego too low-level for small projects?
• Can Plumego scale to high traffic?
• Why is everything so explicit?
• What problems is Plumego not trying to solve?

Each question exists because someone asked it seriously.

If Your Question Is Not Here

If a question is missing:

• Re-read the relevant documentation section
• Check Roadmap and Non-Goals
• Look for design principles that imply the answer

If the question still feels unresolved,
it may be a good candidate for inclusion in the future.

Summary

The FAQ exists to reduce friction, not to sell Plumego.

• It clarifies intent
• It sets expectations
• It reinforces boundaries
• It respects the reader’s intelligence

If Plumego feels strict in its answers,
that strictness is what keeps it coherent.

Next

From here, continue with:

• FAQ / Design Philosophy
• FAQ / Comparisons
• FAQ / Usage Scenarios
• FAQ / Common Pitfalls

Each page addresses a specific class of questions,
without diluting the rest of the documentation.