You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by ma...@jpmorgan.com on 2006/09/07 12:52:29 UTC
Re: Persistence
Hi,
Given this a little thought and am inclined to concur with Colin's point
about shying away from O/R mappers.
Performance is key thus we need to keep very close to any db and possibly
avoid even jdbc style abstraction in the interests of speed.
We could find that providing a pluggable solution compromises the
performance of QPID ? Maybe we need to do both .....
Regards,
Marnie
JPMorgan Chase
BLAZE (QPID) Integration Developer
https://confluence.uk.jpmorgan.com/confluence/display/IBTAMQ/Blaze
This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates.
This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you.
Re: Persistence
Posted by ma...@jpmorgan.com.
Gordon (and all),
Can you share a little on how it's currently implemented/pluggable when
you have a moment please ?
Thanks & Regards,
Marnie
Gordon Sim <gs...@redhat.com>
07/09/2006 16:26
Please respond to dev
To: dev@etp.108.redhat.com, qpid-dev@incubator.apache.org
cc:
Subject: Re: Persistence
The java broker already has a pluggable store for persistence (though of
course new implementations may need/want to make slight modifications to
this). So different options should be achievable.
marnie.mccormack@jpmorgan.com wrote:
>
> Hi,
>
> Given this a little thought and am inclined to concur with Colin's point
> about shying away from O/R mappers.
>
> Performance is key thus we need to keep very close to any db and
> possibly avoid even jdbc style abstraction in the interests of speed.
>
> We could find that providing a pluggable solution compromises the
> performance of QPID ? Maybe we need to do both .....
>
> Regards,
> Marnie
> JPMorgan Chase
> BLAZE (QPID) Integration Developer
> https://confluence.uk.jpmorgan.com/confluence/display/IBTAMQ/Blaze
>
>
> This communication is for informational purposes only. It is not
> intended as an offer or solicitation for the purchase or sale of any
> financial instrument or as an official confirmation of any transaction.
> All market prices, data and other information are not warranted as to
> completeness or accuracy and are subject to change without notice. Any
> comments or statements made herein do not necessarily reflect those of
> JPMorgan Chase & Co., its subsidiaries and affiliates.
>
> This transmission may contain information that is privileged,
> confidential, legally privileged, and/or exempt from disclosure under
> applicable law. If you are not the intended recipient, you are hereby
> notified that any disclosure, copying, distribution, or use of the
> information contained herein (including any reliance thereon) is
> STRICTLY PROHIBITED. Although this transmission and any attachments are
> believed to be free of any virus or other defect that might affect any
> computer system into which it is received and opened, it is the
> responsibility of the recipient to ensure that it is virus free and no
> responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and
> affiliates, as applicable, for any loss or damage arising in any way
> from its use. If you received this transmission in error, please
> immediately contact the sender and destroy the material in its entirety,
> whether in electronic or hard copy format. Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@etp.108.redhat.com
For additional commands, e-mail: dev-help@etp.108.redhat.com
This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates.
This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you.
Re: Persistence
Posted by Gordon Sim <gs...@redhat.com>.
The java broker already has a pluggable store for persistence (though of
course new implementations may need/want to make slight modifications to
this). So different options should be achievable.
marnie.mccormack@jpmorgan.com wrote:
>
> Hi,
>
> Given this a little thought and am inclined to concur with Colin's point
> about shying away from O/R mappers.
>
> Performance is key thus we need to keep very close to any db and
> possibly avoid even jdbc style abstraction in the interests of speed.
>
> We could find that providing a pluggable solution compromises the
> performance of QPID ? Maybe we need to do both .....
>
> Regards,
> Marnie
> JPMorgan Chase
> BLAZE (QPID) Integration Developer
> https://confluence.uk.jpmorgan.com/confluence/display/IBTAMQ/Blaze
>
>
> This communication is for informational purposes only. It is not
> intended as an offer or solicitation for the purchase or sale of any
> financial instrument or as an official confirmation of any transaction.
> All market prices, data and other information are not warranted as to
> completeness or accuracy and are subject to change without notice. Any
> comments or statements made herein do not necessarily reflect those of
> JPMorgan Chase & Co., its subsidiaries and affiliates.
>
> This transmission may contain information that is privileged,
> confidential, legally privileged, and/or exempt from disclosure under
> applicable law. If you are not the intended recipient, you are hereby
> notified that any disclosure, copying, distribution, or use of the
> information contained herein (including any reliance thereon) is
> STRICTLY PROHIBITED. Although this transmission and any attachments are
> believed to be free of any virus or other defect that might affect any
> computer system into which it is received and opened, it is the
> responsibility of the recipient to ensure that it is virus free and no
> responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and
> affiliates, as applicable, for any loss or damage arising in any way
> from its use. If you received this transmission in error, please
> immediately contact the sender and destroy the material in its entirety,
> whether in electronic or hard copy format. Thank you.