WSO2 ESB with added QuickFIX

, ,
1

Imported from previous forum

2

[ original email was from Jim Hunt - jim@marketing-dreams.co.uk ]
It has just come to my attention that the WSO2 open source enterprise service bus is integrated with QuickFIX/J - http://wso2.org/library/3730

I’ve used straight QuickFIX before, but never the Java version. Can anyone enlighten me about the merits (or otherwise!) of QuickFIX/J, particularly when used in combination with WSO2?

Thanks in advance,

Jim

3

It has just come to my attention that the WSO2 open source enterprise service bus is integrated with QuickFIX/J - http://wso2.org/library/3730

I’ve used straight QuickFIX before, but never the Java version. Can anyone enlighten me about the merits (or otherwise!) of QuickFIX/J, particularly when used in combination with WSO2?

Thanks in advance,

Jim

Hi Jim,

I can’t speak to the WSO2 integration, but overall the QuickFIX/J project is a highly-respected open source effort. I know of a number of people that use it both for trading applications, and for testing or productivity tools. Generally speaking, and from our experience using QuickFIX as a component in our Visual FIX platform, the QuickFIX system is a pretty good solution in the mid-latency space. It can depend on how many development resources you have to throw at a problem, but you can get a lot of mileage out of the open source solutions that are available these days.

I don’t do any development on the Java platform, but my experience with the C++/.NET version of QuickFIX has been pretty good. On the other hand, you can also get a tremendous amount of value from commercial vendors if you go with a proprietary solution. If you have really demanding performance requirements, or you need a rich palette of support tools around the FIX engine itself, a commercial solution might be the way to go - the cost of bringing a high-performance engine in house is a lot lower than it used to be, so you can get some really great technology for a lot less than you’d think these days.

Cheers,

Russ

4

[ original email was from Jim Hunt - jim@marketing-dreams.co.uk ]
Hi Russ,

Thanks for your input. A commercial solution might be feasible on another day, but not for this project. The brief is 100% open source, and 100% Java at least to start with.

I too have some experience with the C++ flavour of QuickFIX, but alas none with the Java incarnation. Amongst other things, I was wondering if there are any unpleasant surprises awaiting me as I endeavour to make the switch. You seem to be suggesting that the learning curve won’t be too steep. The overall performance of the two is broadly similar, for example?

Cheers,

Jim

It has just come to my attention that the WSO2 open source enterprise service bus is integrated with QuickFIX/J - http://wso2.org/library/3730

I’ve used straight QuickFIX before, but never the Java version. Can anyone enlighten me about the merits (or otherwise!) of QuickFIX/J, particularly when used in combination with WSO2?

Thanks in advance,

Jim

Hi Jim,

I can’t speak to the WSO2 integration, but overall the QuickFIX/J project is a highly-respected open source effort. I know of a number of people that use it both for trading applications, and for testing or productivity tools. Generally speaking, and from our experience using QuickFIX as a component in our Visual FIX platform, the QuickFIX system is a pretty good solution in the mid-latency space. It can depend on how many development resources you have to throw at a problem, but you can get a lot of mileage out of the open source solutions that are available these days.

I don’t do any development on the Java platform, but my experience with the C++/.NET version of QuickFIX has been pretty good. On the other hand, you can also get a tremendous amount of value from commercial vendors if you go with a proprietary solution. If you have really demanding performance requirements, or you need a rich palette of support tools around the FIX engine itself, a commercial solution might be the way to go - the cost of bringing a high-performance engine in house is a lot lower than it used to be, so you can get some really great technology for a lot less than you’d think these days.

Cheers,

Russ

5

Hi Jim,

at the moment the QuickFIX/J project is API compatible with the QuickFIX project, while it may have some extra additions.

So I wonder which kind of surprises you expect.

We are using QF/J in our productive GLOX environment connecting both our customers to us and connecting to exchanges / brokers using QF/J.

If you have any specific questions, feel free to ask here.

Regards, Jörg

Hi Russ,

Thanks for your input. A commercial solution might be feasible on another day, but not for this project. The brief is 100% open source, and 100% Java at least to start with.

I too have some experience with the C++ flavour of QuickFIX, but alas none with the Java incarnation. Amongst other things, I was wondering if there are any unpleasant surprises awaiting me as I endeavour to make the switch. You seem to be suggesting that the learning curve won’t be too steep. The overall performance of the two is broadly similar, for example?

Cheers,

Jim

It has just come to my attention that the WSO2 open source enterprise service bus is integrated with QuickFIX/J - http://wso2.org/library/3730

I’ve used straight QuickFIX before, but never the Java version. Can anyone enlighten me about the merits (or otherwise!) of QuickFIX/J, particularly when used in combination with WSO2?

Thanks in advance,

Jim

Hi Jim,

I can’t speak to the WSO2 integration, but overall the QuickFIX/J project is a highly-respected open source effort. I know of a number of people that use it both for trading applications, and for testing or productivity tools. Generally speaking, and from our experience using QuickFIX as a component in our Visual FIX platform, the QuickFIX system is a pretty good solution in the mid-latency space. It can depend on how many development resources you have to throw at a problem, but you can get a lot of mileage out of the open source solutions that are available these days.

I don’t do any development on the Java platform, but my experience with the C++/.NET version of QuickFIX has been pretty good. On the other hand, you can also get a tremendous amount of value from commercial vendors if you go with a proprietary solution. If you have really demanding performance requirements, or you need a rich palette of support tools around the FIX engine itself, a commercial solution might be the way to go - the cost of bringing a high-performance engine in house is a lot lower than it used to be, so you can get some really great technology for a lot less than you’d think these days.

Cheers,

Russ

6

[ original email was from Jim Hunt - jim@marketing-dreams.co.uk ]
Hi Jörg,

Thanks very much for the offer. One significant doubt springs from the fact that I was sat at the front of this presentation by Martin Thompson of LMAX (http://vimeo.com/21698758) during which he said “QuickFIX/J is a great FIX engine and it’s reliable” followed at 16:35 by “but it does horrendous things from a performance perspective”! Maybe he was looking at it from the “low latency” perspective, rather than “medium latency”?

I guess I’ll be able to decide for myself on that one in the not too distant future. However I’m still very curious to know if anyone has ever used WSO2 in any way shape or form, because I haven’t and I don’t know anyone else who has either.

Hi Jim,

at the moment the QuickFIX/J project is API compatible with the QuickFIX project, while it may have some extra additions.

So I wonder which kind of surprises you expect.

We are using QF/J in our productive GLOX environment connecting both our customers to us and connecting to exchanges / brokers using QF/J.

If you have any specific questions, feel free to ask here.

Regards, Jörg

Hi Russ,

Thanks for your input. A commercial solution might be feasible on another day, but not for this project. The brief is 100% open source, and 100% Java at least to start with.

I too have some experience with the C++ flavour of QuickFIX, but alas none with the Java incarnation. Amongst other things, I was wondering if there are any unpleasant surprises awaiting me as I endeavour to make the switch. You seem to be suggesting that the learning curve won’t be too steep. The overall performance of the two is broadly similar, for example?

Cheers,

Jim

It has just come to my attention that the WSO2 open source enterprise service bus is integrated with QuickFIX/J - http://wso2.org/library/3730

I’ve used straight QuickFIX before, but never the Java version. Can anyone enlighten me about the merits (or otherwise!) of QuickFIX/J, particularly when used in combination with WSO2?

Thanks in advance,

Jim

Hi Jim,

I can’t speak to the WSO2 integration, but overall the QuickFIX/J project is a highly-respected open source effort. I know of a number of people that use it both for trading applications, and for testing or productivity tools. Generally speaking, and from our experience using QuickFIX as a component in our Visual FIX platform, the QuickFIX system is a pretty good solution in the mid-latency space. It can depend on how many development resources you have to throw at a problem, but you can get a lot of mileage out of the open source solutions that are available these days.

I don’t do any development on the Java platform, but my experience with the C++/.NET version of QuickFIX has been pretty good. On the other hand, you can also get a tremendous amount of value from commercial vendors if you go with a proprietary solution. If you have really demanding performance requirements, or you need a rich palette of support tools around the FIX engine itself, a commercial solution might be the way to go - the cost of bringing a high-performance engine in house is a lot lower than it used to be, so you can get some really great technology for a lot less than you’d think these days.

Cheers,

Russ