SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.
SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.
Successfully reported this slideshow.
Activate your 14 day free trial to unlock unlimited reading.
3.
DROOLS ENABLED MICROSERVICES
AGENDA
▸ What is Drools?
▸ Rule Language / Execution Cycle
▸ Drools & Microservices
▸ Scenario
4.
DROOLS ENABLED MICROSERVICES
ABOUT ME
▸ Mauricio Salatino (aka Salaboy)
▸ Work for Red Hat
▸ Drools & jBPM Community
▸ http://salaboy.com
▸ @salaboy
5.
DROOLS ENABLED MICROSERVICES
WHAT IS DROOLS?
▸ Lightweight Rule Engine (a library)
▸ Rule Engine -> Inference Engine
▸ Change of paradigm from Imperative (Java) to Declarative
6.
DROOLS ENABLED MICROSERVICES
RULE STRUCTURE
▸ rule “Warn on low health”
//<rule attributes>
When
Player( health <= 10 )
Then
// Warning.. find medicine
end
11.
DROOLS ENABLED MICROSERVICES
MICROSERVICES KEY POINTS
▸ Bounded Context - Domain Driven Design
▸ Aligned with the company structure
▸ Small, managed by a team that knows about that
department requirements
▸ Using the right tool for the job ;)
▸ Release Fast - Release Early - Iterate
12.
DROOLS ENABLED MICROSERVICES
DROOLS ENABLED MICROSERVICES
▸ Separate the business logic from technical aspects
▸ Use the bounded context model, no need to change anything,
leverage the scope
▸ Leverage the rule engine features (instead of creating in house
solutions to deal with logical checks and tricky scenarios)
▸ More flexible to business changes
▸ Self documented Micro Services
▸ Micro services that provides justification for each decision made out-of
the-box