Hi all
Being very new to Jess and expert system generally speaking. We will
need some helps to clarify my thought of how Jess can use and deploy
specifiically to a Web base 3 tier architecture. We are very much into
development web base solution using technologies such as JSP, Servlet, EJB,
DB, LDAP etc. Traditionally, most logics (application or business) are coded
within the programme. Each time we need to modify the flow or logic, we need
to amend the related code (can result in a tremendous amount of work) and
redeployed each time. These are somehow not very acceptable in a production
environment and not cost effective at all.
We are seriously looking into how we can extract business rules, flows,
action and reaction etc and to store them externally. The followings are our
concerns and thoughts and we hope some inputs, advises and comments.
In most samples, we are seeing only a copy of Rete running. In a web
base environment, we are looking into managing multiple unrelated request at
the same time. For example, login sequence, 10 requests for login into a
portal/web site. Assuming that all 10 requests will need the same sequences
of validation (business logic for validation).
Q1. If all 10 requests leverage on the same Rete instance, am I
correct to say that the single instance of Rete can only serve 1 request at
one time and thus the rest of 9 will need to be queue? Performance issue?
Q2. Can or should we instantiate Rete for each request and resulting
in 10 independent instances of Rete? Performance issue?
Q3. Pertaining to Q3, will performance be improve if we load rules
specific to type of application (login validation)? Or should we pool a sets
of Rule engine?
Q4. We are looking into storing rule LHS and RHS into RDBMS (or LDAP
compliance server) database and map them to application type and loaded upon
need. Therefore we can change the rule without any further recompilation and
deployment? Why database? We are looking in having this solution run in a
cluster environment to faciliate load balancing and fail-over capabilities.
We are still in the midst of designing a framework to fit the above
thoughts. Any advise will be greatly appreciated. Thanks!
Regards
Aloysius
---------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the
list (use your own address!) List problems? Notify [EMAIL PROTECTED]
---------------------------------------------------------------------
