liveBook · Manning

Convention over configuration

Convention over configuration is a software design approach in which established conventions provide defaults, requiring explicit configuration only for deviations.

How 3 Manning books explain it

ASP.NET Core in Action, 3e

Convention over configuration is a design approach in which framework-defined naming and structure conventions determine behavior unless explicitly overridden.

How it is used
Uses framework naming and structure conventions to reduce explicit mapping and guide API-style decisions.
How deep it goes
Explains default entity discovery, keys, foreign keys, and relationships, but defers most naming and column conventions.
Examples
Uses Recipe and Ingredient classes, a RecipeId key convention, an Ingredient RecipeId foreign key, and API-style comparison criteria.
What you can do after
Evaluate EF Core entity shapes and choose between minimal APIs and web API controllers using convention preference and technical needs.

Read how ASP.NET Core in Action, 3e explains convention over configuration →

Spring Start Here, Second Edition

Convention over configuration is a software design approach in which standard conventions supply defaults and explicit configuration is needed only for deviations.

How it is used
Reduces setup for Spring web applications by supplying defaults for requested capabilities.
How deep it goes
Defines default configuration and explains dependency-driven Tomcat setup, but does not detail configuration mechanisms for deviations.
Examples
Uses a web dependency to trigger Tomcat configuration and a startup log showing port 8080.
What you can do after
Operate/configure a Spring Boot application using defaults and changing only settings that differ from convention.

Read how Spring Start Here, Second Edition explains convention over configuration →

Quarkus in Action

Convention over configuration is a software design pattern in which framework conventions provide defaults so applications need to specify only deviations.

How it is used
Reduces configuration and boilerplate when building Java applications with frameworks such as Quarkus or Spring Boot.
How deep it goes
Defines defaults and overrides through framework examples but stops short of detailing configuration mechanics or implementation internals.
Examples
Uses Quarkus JVM defaults and Spring Boot standalone applications as concrete examples of convention-driven frameworks.
What you can do after
Apply framework defaults and override only the functionality that differs from the conventional behavior.

Read how Quarkus in Action explains convention over configuration →

Also covered in

What to know first

Related concepts

Questions about convention over configuration

What is convention over configuration?

Convention over configuration is a software design approach in which established conventions provide defaults, requiring explicit configuration only for deviations.

Which Manning books explain convention over configuration?

ASP.NET Core in Action, 3e, Spring Start Here, Second Edition and Quarkus in Action.

What should I know before learning convention over configuration?

Manning books that teach convention over configuration usually introduce Jakarta EE, Java and object-relational mapper first.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.