Source Notes

This repo is original guidance informed by the following sources. It does not reproduce book text.

Primary Project Source

• leonardolemie/clean-code-java provided the original guide shape and MIT-licensed starting point.

Official Akka Sources

• Akka SDK documentation
• Akka architecture and project structure
• Running an Akka service locally
• Designing HTTP endpoints
• Implementing key value entities
• Implementing workflows
• Implementing views
• Agents

Book Influences

The local references listed by the repository owner were used as conceptual input:

• Robert C. Martin, Clean Code and The Clean Coder
• Robert C. Martin, Clean Architecture
• Robert C. Martin, Clean Agile
• John Ousterhout, A Philosophy of Software Design

The adaptation emphasizes:

• Meaningful names, small functions, clean tests, and boundary discipline.
• Dependency direction and use-case-centered architecture.
• Small increments, acceptance tests, refactoring, and simple design.
• Complexity reduction, information hiding, deep modules, and layer-specific abstractions.

Adaptation Policy

• Prefer Akka SDK terminology over generic Java terminology.
• Prefer business examples over framework-only examples.
• Prefer current official Akka docs for API-specific claims.
• Avoid copying book prose.
• Treat component ids, event names, routes, topics, and persisted state as contracts.