Business logic
Business logic is the domain-specific rules, computations, and decisions that determine how a software system behaves and processes operations.
Simple Object-Oriented Design: Create clean, maintainable applications
Business logic is the set of rules and behavior that implement an application's problem-domain requirements.
- How it is used
- Places problem-domain rules in backend entities and services while keeping external communication outside them.
- How deep it goes
- Explains class extraction, data generalization, infrastructure boundaries, testing effects, and coupling tradeoffs without detailing cache implementation.
- Examples
- Uses Enrollment cancellation, author lists and discounts, configuration files, and cached employee repository lookups.
- What you can do after
- Evaluate/understand where domain rules belong and refactor infrastructure or retrieval concerns behind focused boundaries.
Functional Design and Architecture: Examples in Haskell
Business logic is the set of domain rules and application behaviors that determine how a system responds to business situations.
- How it is used
- Organizes domain workflows apart from HTTP, databases, logging, and other operational layers.
- How deep it goes
- Defines the boundary and works through layered scripts, interfaces, and a web-handler refactoring; it defers universal architectural conclusions.
- Examples
- Uses sandwich assembly, meteor reporting, logger calls, and an astronomical-object database lookup.
- What you can do after
- Evaluate/understand how to move domain behavior behind interfaces and run it from application boundaries.
Read how Functional Design and Architecture: Examples in Haskell explains business logic →
Practices of the Python Pro
A business logic layer is a software layer that contains application rules and operations governing how inputs are transformed into business outcomes.
- How it is used
- Organizes application-specific actions between user-facing presentation and data-storing persistence layers.
- How deep it goes
- Demonstrates commands for CRUD operations and discusses coupling, while deferring broader implementation beyond the application example.
- Examples
- Uses Bark’s bookmark commands for creating tables, adding, listing, deleting, and importing or extending application functionality.
- What you can do after
- Build it from scratch by separating application actions into commands that coordinate presentation input and persistence operations.
Read how Practices of the Python Pro explains business logic →
ASP.NET Core in Action, 3e
Business logic is the application behavior that implements domain rules, decisions, and processes independently of presentation or infrastructure concerns.
- How it is used
- Organizes application rules and processes behind handlers in server-rendered applications and HTTP APIs.
- How deep it goes
- Defines separation and service responsibilities, then stops short of detailing domain internals or advanced architecture.
- Examples
- Uses RecipeService operations, MVC product and shopping-cart interactions, and currency-conversion controller tests.
- What you can do after
- Build it in services that handlers call, then unit-test the behavior separately from HTTP framework systems.
Read how ASP.NET Core in Action, 3e explains business logic →
Data-Oriented Programming: Reduce software complexity
Business logic is the domain-specific rules and computations that determine how an application processes requests and data.
- How it is used
- Structures request and response processing while keeping domain rules distinct from generic data manipulation.
- How deep it goes
- Explains separation, named utilities, tests, and implementation steps, but stops short of broader domain modeling.
- Examples
- Demonstrates book lending ratios, nested book-item data, countByBoolField, Lodash reduce, and a focused unit test.
- What you can do after
- Build it from scratch by extracting named data utilities, testing them, and expressing business intent concisely.
Read how Data-Oriented Programming: Reduce software complexity explains business logic →
The Art of Code
A business logic error is a failure caused by incorrect implementation of the application's domain rules or intended behavior.
- How it is used
- Classifies rule violations so applications can anticipate them and respond with clear, user-friendly recovery paths.
- How deep it goes
- Defines the category and response principles, but stops short of implementation patterns or detailed validation code.
- Examples
- Uses invalid forms, expired discounts, unsupported files, duplicate emails, excessive login attempts, and oversized avatar images.
- What you can do after
- Evaluate failures by category and design explicit validation, communication, translation, recovery, or fallback behavior.
Building User-Friendly DSLs
The rules and decision-making behavior that encode an organization’s business knowledge in software.
- How it is used
- Computes customer-facing price quotes from rental inputs and organizational pricing policies.
- How deep it goes
- Explains rules, nested conditionals, and intermediate state, but defers a precise definition of business rules.
- Examples
- Uses car-rental pricing with holiday surcharges, weekly discounts, environmental fees, car rates, and contract types.
- What you can do after
- Evaluate how business knowledge becomes conditional software behavior for a car-rental price quote.
Read how Building User-Friendly DSLs explains business logic →
.NET MAUI in Action
Business logic is software logic that represents an application's business rules, processes, and decisions.
- How it is used
- Separates domain behavior from UI and presentation code so applications remain reusable, maintainable, and less tightly coupled.
- How deep it goes
- Defines models, rules, queries, and services, then demonstrates their placement in an MVVM application without detailing implementation internals.
- Examples
- Uses product searches, inventory counting, user-input rules, domain models, and services communicating with REST or GraphQL APIs.
- What you can do after
- Apply it via MVVM by placing domain behavior in models or services and exposing required functionality through ViewModels.
Unit Testing Principles, Practices, and Patterns
The set of rules and decisions that implement an application's domain-specific behavior.
- How it is used
- Prioritizes unit-testing effort around domain behavior because it offers the strongest return on time invested.
- How deep it goes
- Defines testing priority and isolation boundaries, but defers detailed implementation techniques.
- Examples
- Contrasts domain models with databases, third-party systems, infrastructure code, and application glue.
- What you can do after
- Apply unit testing to isolated domain behavior and use integration tests for broader system interactions.
Read how Unit Testing Principles, Practices, and Patterns explains business logic →
Shipping Go: Develop, deliver, discuss, design, and go again
Business logic is the application logic that implements domain rules and required business behavior.
- How it is used
- Uses a service to convert application requests into domain-specific results before handlers and servers return them.
- How deep it goes
- Defines a small service boundary and test cases, but stops short of detailing complex domain rules or implementation internals.
- Examples
- Uses a translation service, Translate function, and cases for English, capitalization, and extra spaces.
- What you can do after
- Diagnose behavior by isolating the service and asserting outputs against given-when-then cases.
Read how Shipping Go: Develop, deliver, discuss, design, and go again explains business logic →
Related concepts
- business ruleincludes · A business rule is a domain-specific policy, condition, or constraint that governs valid data, decisions, actions, or behavior in an organization or its systems.
- handlerused by · A handler is a callable or software component that processes an event, request, message, or other input and performs associated processing.
- testused by · A test is a procedure or check that evaluates behavior using specified inputs or evidence against expected results or criteria.
- infrastructurecontrasts with · Infrastructure is the foundational physical, digital, and operational resources and systems that support an organization, computing system, or service.
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.