It's pretty old, but you've got some architectural diagrams here: <a href="http://www.infoq.com/articles/Rule-Engines">http://www.infoq.com/articles/Rule-Engines</a><br><br><div class="gmail_quote">On Wed, Jan 26, 2011 at 12:27 PM, Sebastien Chevalier <span dir="ltr"><<a href="mailto:Sebastien.Chevalier@web.de">Sebastien.Chevalier@web.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><br>
@plugtreelabs: First of all, thank you very much for your response and hints.<br>
<br>
@all: As I'm still not quire sure how to realize my scenario:<br>
Please, could someone provide me with some diagrams or architectural<br>
sketches of a typical rules-based e-commerce web application? -- Or at least<br>
point me to online resources on that topic, especially showing the<br>
integration of the RBMS in a web app?<br>
<br>
This would really help me out a lot at the moment.<br>
<br>
_Recap:<br>
The main goal is that endusers shall, on the one hand, define almost the<br>
whole set of entities and rules in an initial shop<br>
specification/configuration process, and on the other hand, this set shall<br>
be modifiable later on (primarily through enhancements, not restrictions).<br>
The entity set basically is: customer types, product categories, products,<br>
product packages, customer(type)-to-product(type) price assignments (i.e.<br>
pricing rules), and inter-product/package selection rules, ...all of these<br>
dynamically definable via a WebUI and in a manner appropriate for<br>
non-technical end-users (considering declarative programming a good approach<br>
for this(?)).<br>
<br>
The most dynamic parts will be the multi-dimensional pricing tables in terms<br>
of (a) their schema -- when new pricing parameters (=dimensions) like<br>
delivery distance are added -- and (b) their value contents -- when concrete<br>
prices change.<br>
Another quite dynamic part will be the inter-product selection rule<br>
specifications from which a "smart" e-catalog will be generated for the<br>
client-side. Such rules will state sth. like:<br>
"Prod A must always be ordered with Prod B", "Prod B can never be ordered<br>
when Package C is selected", and similar.<br>
--<br>
<br>
Currently, some "high-level architectural layouts" of a simple, rules-based<br>
e-commerce web app (Which components are necessary in which place? And which<br>
components are already delivered by Drools?) would be very helpful for me.<br>
<br>
Thank you very much for your help in advance.<br>
<br>
Best regards<br>
Sebastien<br>
<font color="#888888"><br>
--<br>
View this message in context: <a href="http://drools-java-rules-engine.46999.n3.nabble.com/Is-Drools-appropriate-for-this-app-scenario-tp2303204p2353169.html" target="_blank">http://drools-java-rules-engine.46999.n3.nabble.com/Is-Drools-appropriate-for-this-app-scenario-tp2303204p2353169.html</a><br>
</font><div><div></div><div class="h5">Sent from the Drools - User mailing list archive at Nabble.com.<br>
_______________________________________________<br>
rules-users mailing list<br>
<a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
</div></div></blockquote></div><br>