Ashesh Badani talks about systems convergence

The explosion of data and cloud-based application deployments in businesses today are driving a convergence between event-driven architecture, business rules and business process management (BPM), said JBOSS middleware expert Ashesh Badani in an interview at JavaOne 2010. In this video, Badani -- Red Hat's senior director of JBOSS Enterprise Middleware -- connects the dots between these trends and practices.

Read the full transcript from this video below:  

Ashesh Badani talks about systems convergence

Hi, my name is Ashesh Badani. I'm Senior Director for JBoss Enterprise Middleware at RatHat. One thing I want to talk to you today about is the convergence that we're seeing in the marketplace between areas that you may not have thought were working together.

So, people have been doing business process management for a long time, they've been using propriety tools, and then they've been using a lot of standard based business process management, especially with the advent of service oriented architectures. So, people are being successful. We're seeing an increasing trend with BPMN going forward and we at RatHat and at JBoss are focusing on ensuring that we're giving users the most productive environment.

Another trend that we've seen which is sort of leading us to the convergence is a great adoption of business rules; this is because there's an explosion of data in the market place, right, with more and more internet usage, more and more cloud-based deployments coming into play. There's more data being generated, right. Facebook is serving up 2 million web requests a second.

So, along those lines, we're seeing interest in business rules and in the need for people to essentially work their business rules in conjunction with business processes, as opposed to treat them separately. So, with the notion that event-driven architectures have really come into play today, the triggering of certain events leads to a kickoff of business rules based on the parameters that have been set in place, and that can ultimately trigger off a business process.

One example would be that if there's a lot of data and web requests coming to a website for a particular product, you recognize that you're out of stock for that, you want to make sure that you go pull it from, let's say, a suppliers who's a partner who is not in your preferred list. That can all be written up as a sort of business rules when those events are triggered and you receive that information, certain thresholds are passed, you can then go up and pick a business process that allows you to open up a P.O., and be able to order those missing parts so you can fulfill customer demand.

This is the world that we live in today and we expect to see an increasing convergence between event-driven architecture, business rules, and business process management; and the next releases of our products will ensure that you'll see more a manifestation of that and you can start deploying in your department.