liveBook · Manning

Business logic

As explained in Spring Start Here, Second Edition

Business logic comprises the domain-specific rules and processes governing an application's core operations.

Business logic is the code that implements an application's business requirements and user expectations. It gives an application its distinctive functionality, unlike shared plumbing such as logging, security, transactions, and caching. section 1.1

From user need to business logic

When a user clicks a link to generate an invoice, the code that makes the invoice appear implements business logic. Requesting a car or ordering a pizza are other examples of user-facing use cases. section 1.1

Figure 1.2 The user’s perspective is like viewing an iceberg. Users mainly observe the results of the business logic code, but this is only a small part of what builds the app’s complete functionality. Like an iceberg that is mostly underwater and hidden from view, we don't see most of the code in an enterprise app because it's provided by dependencies.

The iceberg analogy shows that users mainly see the results of business logic, while much of an application's supporting code remains hidden. section 1.1

How Spring Start Here, Second Edition covers it

How deep it goes
Defines the term, distinguishes it from shared plumbing, and illustrates it with invoice and use-case examples.
Examples
Uses invoice generation, requesting a car, and ordering a pizza as examples of user-facing functionality.
What you can do after
Understand which code implements user-facing requirements and which supports shared application infrastructure.
How it connects
Connects business logic to application frameworks, use cases, and plumbing code.

Also explained in

Compare how 15 books explain business logic →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Spring Start Here, Second Edition. The section links point to the parts of the book it draws on.