Software Business Layer
Jump to navigation
Jump to search
A Software Business Layer is a software architecture layer that implements business logic (to support business processes through rule processing).
- AKA: Domain Layer, Logic Layer, Process Layer.
- Context:
- It can typically process Business Rules through rule engines.
- It can typically execute Business Transactions through transaction managers.
- It can typically validate Business Data through validation engines.
- It can typically maintain Business State through state managers.
- It can typically enforce Business Constraints through constraint checkers.
- ...
- It can often implement Workflow Processing through workflow engines.
- It can often provide Decision Making through decision engines.
- It can often manage Business Events through event processors.
- It can often support Domain Logic through domain services.
- ...
- It can range from being a Simple Process Engine to being a Complex Rule Engine, depending on its logic complexity.
- It can range from being a Sequential Processor to being a Parallel Processor, depending on its processing pattern.
- It can range from being a Stateless Service to being a Stateful Service, depending on its state management.
- ...
- It can integrate with Persistence Layer for data access.
- It can connect to External System for business integration.
- It can utilize Business Framework for logic development.
- ...
- Examples:
- Banking Systems, such as:
- E-commerce Systems, such as:
- Workflow Systems, such as:
- ...
- Counter-Examples:
- Data Access Layer, which handles data persistence rather than business logic.
- User Interface Layer, which manages user interaction rather than process execution.
- Infrastructure Layer, which provides technical services rather than business services.
- See: Business Process Pattern, Domain Logic Pattern, Transaction Processing Pattern, Business Rule Engine.