Posted: Wed Feb 27, 2008 2:17 am Post subject: WMB Coding best practice
Centurion
Joined: 10 Apr 2007 Posts: 132 Location: Germany
I'm still missing a Redbook "WMB for the Application Programmer". Due to the fact that the WMB isn't that spread and the use of ESQL either there is a lack of information in my opinion.
For example project organisation, is it wise to keep all db-actions in a utilities schema and reference it from the rest of the code?
What about naming conventions? All db-actions that update start with update, ...
Another issue is the granularity within a msgFlow. If I receive a msg store it, transform it and pass it on, should I use one big compute node to do all the work, or one node for each task, ...
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum