Interface Logic Versus Business Logic
In developing services, it is common to distinguish interface logic from shared business logic:
In developing services, it is common to distinguish
interface logicfrom shared
- Interface LogicInterface logic is logic that is specific to a service. When you require logic specific to a service, you can define resources explicitly in your API, and then extend them, for example, with request event handlers, request/response transformation, or metadata action tags.The Business to Business (B2B) sample includes many of the concepts that describe interface logic in the resources that you define explicitly in your API and practical samples.For more information about the B2B sample, see Business to Business Example.
- Business LogicBusiness logic is logic that you define for entities (tables and views) as reactive logic.CA Live API Creatorshares this logic across all resources that you define explicitly in your API and associates it with the row objects. This automatic sharing is a consequence of the resource/row mapping that is described in logic execution.Business logic describes the business logic for your API, expressed by reactive logic such as:
Best Practice:Because business logic is the point of highest reuse, use it to the maximum practical extent.For more information:
- Validation rules: Expressions that are assigned to an entity that must be true for a transaction to commit (else the transaction is rolled back and a suitable message is returned to the client).
- Derivation rules: Spreadsheet-like rules for table/column derivations. For example, formula rules, sum rules, and parent copies. The rules chain to address multi-table transactions.
These concepts of interface logic and business logic exist in
CA Live API Creator:
Point-and-click resource creation (including joining data from multiple databases).
Provide APIs for API consumers with more interface logic to optimize output and reduce latency.
Match external API agreements, particularly in the request and response formatting, for both retrievals and updates.
Entities (Tables and Views)
Spreadsheet-like validations and derivations (for example, formulas, sums, and counts).
Extend with row event handlers.
Business logic and security, which API Creator automatically invokes and re-uses across resources.
Validations and row event handlers fire only on update operations.