|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
WBIMB vs BizTalk |
« View previous topic :: View next topic » |
Author |
Message
|
zpat |
Posted: Tue Jul 19, 2011 7:46 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
Using non-persistent messages on a queue is quite efficient as a form of cache. |
|
Back to top |
|
 |
Vitor |
Posted: Tue Jul 19, 2011 7:51 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
zpat wrote: |
Using non-persistent messages on a queue is quite efficient as a form of cache. |
Urgh. The "a queue is not a database table" debate gallops towards us... _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
lancelotlinc |
Posted: Tue Jul 19, 2011 8:38 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
Vitor wrote: |
lancelotlinc wrote: |
Support pac IA91 is the last resort for caching WMB infos. You will fair better using Singletons and HashMaps. |
There you are! Got worried when this didn't evoke a reaction... |
I miss you too, buddy. _________________ http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
Back to top |
|
 |
zpat |
Posted: Tue Jul 19, 2011 9:35 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
Vitor wrote: |
zpat wrote: |
Using non-persistent messages on a queue is quite efficient as a form of cache. |
Urgh. The "a queue is not a database table" debate gallops towards us... |
So what you are saying is that IBM are also wrong to move from using broker database tables to queues for in flight temporary data storage? |
|
Back to top |
|
 |
Vitor |
Posted: Tue Jul 19, 2011 9:46 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
zpat wrote: |
So what you are saying is that IBM are also wrong to move from using broker database tables to queues for in flight temporary data storage? |
No, I'm talking about the historic posts where some design loads up a queue with messages then an application does a browse by message id to retrieve the data. In many cases the message id is a piece of business data in string format. Usually they post here because they've either moved the application to a different code-paged platform and the "select" doesn't work properly or it works but it runs like a snail on Valium towing an anvil once they hit 5000 messages.
And they always got annoyed when we suggested using a database instead. I twitch every time someone mentions Java selectors (which are not quite the same thing I think)
Queues for storage? Yes. Queues as a database table? No. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
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
|
|
|
|