Like a database we index our data to provide high performance. There are two types of indexing - Alpha Node hashing and Beta Node indexing. Alpha Node hashing is used to index literal constriants, so that we only propagate the data to the rules that match that literal value. Beta Node indexing is used to index data used in joins - we have two facts, person and cheese, we record who owns which cheese and there is a rule that says "when the person's cheeses are out of date then email that person" we have a join between the person and the cheeses, so we index each cheese against its owner. We also attempt to share indexes, so if rules use the same literals or joins where possible we try and share those indexes - this reduces memory consumption and also avoids duplicate constraint evaluations.
However a Production Rule system provides many features beyond a traditional database. Many of the features, marked with a * are planed for JBoss Rules releases next year.
Firstly, before ORM advocates try and organise a public lynching, let me just state that "Beyond ORM" does not mean to replace ORM, there are clearly many applications where ORM is preferable - particularly when dealing with truly massive datasets or where you want to be able to represent relational data in differing form. However there are situations which can benefit from a richer and better integrated solution with features as described above. There is still a lot of work to achieve all of the above and we then need to consider how to cluster working memories to provide fault tolerance and some way to also make working memories transactional. If we can solve those problems we can look to integrate JBoss Cache, JBoss Rules and JBoss ESB for a next generation Data Centre. This is is a long term R&D proposal, but I thought I would sketch down the basic ideas in the diagram below.