Our unique declarative approach uses spreadsheet-like business abstractions, so...
Instead of writing 500 lines of code, you can declare the 5 rules shown below
Too good to be true? Check out this example...
| Just declare business-oriented rules like:|
Constraint: balance < creditLimit
balance = sum(orders.total
where paid = false)
order.total = sum(lineitems.amount)
lineitem.amount = quantity * partPrice
lineitem.partPrice = copy(part.price)
automatically ordered, re-used and optimized..
... every time you make a change. Download the product (includes sample) Compare to the 500 line manual alternative
Easy to Adopt
Components: fit easily into your architecture / framework. Logic Injection is via Hibernate Events - no code generation, no recoding (uses existing Hibernate APIs), no changes to Domain Objects. Business Logic is often half your app. So turning 500 lines of code into 5 rules means you get to market faster, and respond to change faster.
And, business logic looks like spreadsheet formulas, so it is transparent to both IT and business Users. Such a common language facilitates communication, and can reduce Requirements Risk.
Maintenance Automation: Declarative means you specify what, the system automates the when and how. Fully automated dependency analysis / ordering - each time you change logic.
Performance automation reduces hardware costs, and tuning effort.
|How it works|
Automated Business Logic is a runtime engine that plugs into Hibernate update events, executing declarative logic you supply in logic classes that parallel your Hibernate POJOs.
This encapsulates your business logic, with no change to data access APIs or POJOs.
The video depicts Automated Business Logic Operation and Architecture, using the sample described above.
| || |
How to use it
See how to use Automated Business Logic:
- Defining Business Logic
- Using the debugger