+1 vote
in Interview Questions by (16.1k points)

1 Answer

+1 vote
by (960 points)
selected by
Best answer
it depends on your situation, if your queries need in-processing data which help doing some calculations to get the final result from the main query, and your business process is not interested in all of these data, the stored procedures will be perfect to you because retrieving those data to the BPM engine would be a waste of your resources, beside querying data is much faster inside the DB engine, and if not, direct sql query will be sufficient for you, that's for performance.

for business and logic, BPM is created to utilize business and use cases, if your statement is tightly coupled with the business and adds value to who's trying to understand it, then sql query is a way better to go, if it goes with separate logic or functionality, that doesn't  directly affect the high level business, stored procedures may be achoice here.

for example if a BPM bank system is trying to query the core for customer's balance, the balance is what really matters to you, nothing else.

Related questions

0 votes
1 answer 95 views
0 votes
1 answer 306 views
0 votes
0 answers 121 views
–1 vote
1 answer 227 views
asked Dec 5, 2019 in Toolkits by taurora (530 points)
0 votes
1 answer 189 views
0 votes
1 answer 210 views

582 questions

482 answers


1.7k users

Dosvak IBM BPM /BAW Products, Download Evaluation
Process & Performance Tools Process & Performance Tools
Code Analyzer Code Analyzer
UI Toolkit UI Toolkit
Integration Monitoring Integration Monitoring
Welcome to BPM Tips Q&A, Community wiki/forum where you can ask questions and receive answers from other IBM BPM experts and members of the community. Users with 2000 points will automatically be promoted to expert level.
Created by Dosvak LLC
Our Youtube Channel