| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Which one is better - Compute nodes or Database Nodes ? |
« View previous topic :: View next topic » |
| Author |
Message
|
| fjb_saper |
 Posted: Fri Nov 27, 2009 7:36 am Post subject: |
 |
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20767
Location: LI,NY
|
| smdavies99 wrote: |
How about Depreciated?  
(only joking) |
Didn't know you considered it an asset on the balance sheet. Unless you meant Deprecated? 
_________________
MQ & Broker admin |
|
| Back to top |
|
 |
| mqmatt |
| Posted: Fri Nov 27, 2009 8:06 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| Well, with DatabaseRoute/DatabaseRetrieve etc., one could argue that the Database node is now worth less than its original value... |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Nov 27, 2009 8:42 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| mqmatt wrote: |
| Well, with DatabaseRoute/DatabaseRetrieve etc., one could argue that the Database node is now worth less than its original value... |
Or that this is again a reason to change the name to better indicate the function we're encouraging customers to use it for. |
|
| Back to top |
|
|
| sirsi |
| Posted: Sat Nov 28, 2009 6:29 pm Post subject: |
|
|
Disciple
Joined: 11 Mar 2005
Posts: 177
|
mqk wrote:
| Quote: |
| I should point out that cost of the extra message creation is very tiny, and should not really be used as a big factor when deciding which node to use. |
if there is not much difference in performance the filter, db nodes should be deprecated and compute should be renamed as 'all purpose node' ...
i believe all these nodes call internal c++ core MB methods, looks like its method overloading of compute node method!!! |
|
| Back to top |
|
|
| nathanw |
| Posted: Thu Dec 17, 2009 8:40 am Post subject: |
|
|
Knight
Joined: 14 Jul 2004
Posts: 550
|
going back to the original days etc if memory serves me correctly, the original node was a compute node and from this sprang forth all the other nodes that exist today (within reason)
once a function was designed within the compute node and tested the decision was then made whetehr or not to create a separate node for teh function, hence the different nodes available and teh ability to carry out those specific node functionality within the compute node
in the past I have had small flows with a compute node that carries out many functions and vice versa, in the end it all depended not on teh performance but on the support ability of the users ie could they debug a single node or would they need step by step processing.
it also depends on the developer of the flow and how they actually fo about developing it ie from start to finish with each step in mind
just my 2 penneth
_________________
Who is General Failure and why is he reading my hard drive?
Artificial Intelligence stands no chance against Natural Stupidity.
Only the User Trace Speaks The Truth  |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
