Tag Archives: Drools

Drools Workshops LATAM 2015

Yesterday, I’ve finish my trip and my last workshop here in Buenos Aires. I would like to thank all the people that made it possible from Chile and Argentina. In these last two weeks I’ve met wonderful people looking forward to use Drools in very advanced scenarios. I’m quite happy with the results because more and more people is trying to use Drools in very different ways to solve very different problems, but they share all the same passion. They all understand how and why Drools (& jBPM) can really help to facilitate how we can build flexible applications that decouple the business logic layer, so it can be updated to reflect the company changes when it is needed.

Continue reading

Tagged , , , , , , , , ,

Back to Basics #5: Cloud Rules (Drools & Docker)

On this blog post we are going to take the microservice created in my previous post and we are going to use Docker bundle it and run it. As you might know already, this is not Drools Specific, but we are going to use all these infrastructure to build our Rule Enabled Microservices in future posts, so having a very basic example on how to use Drools surrounded by all these new technologies will help to set the stage for more complex Drools Examples.

The main goal of this post is to show how, by using Docker, we can share Drools enabled application reducing the amount of components to install to get our Rule Engine instances up and running. Basically by the end of this post you will see Docker in action, and how you can run the same micro service in your environment by just having Docker installed.

Continue reading

Tagged , , , , , , , , , , ,

Back To Basics #4: Exposing our Rules via REST (JAX-RS) using Wildfly Swarm

It is a common requirement nowadays to access to our Rule Engine Instances as REST services. On this blog post I will show an extremely simple example on how you can expose your domain specific interfaces that you can use to encapsulate KieSessions. This post builds up on my previous three posts: first, second, third.

We will be using Wildfly Swarm to create a Fat-Jar that we will be able to run without the need of installing a full blown Java EE application Server. This approach is very good when you need full control about the REST interfaces that you want to expose to  your client applications. For a more general use and for an already built in approach you can take a look a the new KIE Server, something that I will cover in future posts as well.

Continue reading

Tagged , , , , , , , , , , , , ,

Get every new post delivered to your Inbox.

Join 1,117 other followers