# The app

Source: https://docs.anetos.dev/concepts/the-app/

- [Glossary](https://docs.anetos.dev/concepts/glossary/index.md): The words these pages use, what each means in Anetos, and the words other frameworks use for the same thing when they differ. Anetos uses the word Go developers already know for Go-shaped things, and the word web frameworks share for framework concepts. A new word appears only for a new idea, and is listed here.
- [Application lifecycle](https://docs.anetos.dev/concepts/application-lifecycle/index.md): An Anetos application goes through five phases: **New → Register → Boot → Run → Shutdown**. Knowing which code runs in which phase tells you where to put configuration, wiring, connections and cleanup.
- [Runtime supervisor](https://docs.anetos.dev/concepts/runtime-supervisor/index.md): Every Anetos application runs its long-lived work (HTTP servers, queue workers, pub/sub listeners, the scheduler, background tasks) as goroutines inside one process, managed by a **supervisor**. It decides what runs, what happens when something fails, and how everything stops.
- [Commands and the app binary](https://docs.anetos.dev/concepts/commands/index.md): Your app builds to one binary that is both the server and its maintenance tool. `app.Execute()` reads the first argument and runs that command: `run` by default, or `serve`, `migrate`, `route:list` and commands of your own. Code generation lives elsewhere, in the `anetos` developer tool, because it writes source code rather than running the app.
- [Configuration](https://docs.anetos.dev/concepts/configuration/index.md): Where settings come from, how they become typed Go structs, and why a bad setting stops the app before it serves a single request.
- [Code generation](https://docs.anetos.dev/concepts/code-generation/index.md): Queries in Anetos name columns with typed Go values, such as `PostCols.Title`, that `anetos generate` writes from your model structs. The compiler checks every column name and every value's type, and nothing has to look a column up at query time.
- [How testing works](https://docs.anetos.dev/concepts/testing/index.md): What `anetostest` builds for a test, how it keeps tests from seeing each other's data, how its client imitates a browser, and where a test run differs from production.
- [Performance](https://docs.anetos.dev/concepts/performance/index.md): What a request costs in Anetos, where the time goes in a real page, and how the framework is kept from getting slower. The numbers come from the repository's benchmarks, with their method and code: [docs/benchmarks/v0.3.md](https://github.com/anetos-dev/anetos/blob/v0.5.0/docs/benchmarks/v0.3.md).
