问题描述
我正在编写基于quickfixj的FIX buyside GUI。虽然性能不是GUI的问题，但我正在考虑将quickfixj从Mina迁移到Netty，因为我希望将它开发到一个buyside引擎。 quickfixj的性能不满意我。据说Netty在性能方面比Mina好。
有没有人知道Java平台上有没有其他开源FIX引擎（因为quickfixj中有很多错误）？我想知道哪一个是更好的选择，迁移或其他FIX引擎？
I am writing a FIX buyside GUI based on quickfixj. Although the performance is not an issue to a GUI, I am thinking of migrating the quickfixj from Mina to Netty as I would like to develop it to a buyside engine. The performance of quickfixj is not satisfied with me. It is heard that Netty is better than Mina on performance.
Does anyone know is there any other opensource FIX engine on Java platform(because of many bugs in quickfixj)?I am wondering which one is a better choice, migration or another FIX engine?
推荐答案
我不确定您在实施Netty而不是Mina时期望获得多少性能QuickfixJ。有时我们需要考虑易于适应性和可维护性而不仅仅是性能。我使用quickfix和quickfixJ实现了一个修复引擎，Java版本在支持更多消息方面更复杂。那么性能比预期的要多，大约超过300条消息/秒。
I am not sure how much perfomance gain you are expecting from implementing Netty rather than Mina in QuickfixJ. Sometimes we need to look at ease of adaption and maintainability rather than only perfomance. I implemented a fix engine using both quickfix and quickfixJ, the Java version was more complex in term of more messages being supported. Well the perfomance was more than was expected, went through around more than 300 messages/sec.
关于QuickfixJ是错误的，是的，但是你有源代码你可以根据需要修改它。我不知道任何其他开源Java修复引擎。供应商支持Quickfix，如果您打算购买它，他们会支持Quickfix中的任何错误。
Regarding the QuickfixJ being buggy, yes it is, but you have the source code you can modify it as you want. I don't know of any other open source Java fix engine. And Quickfix is supported by vendors, if you intend to buy it they would be there to support any bugs in Quickfix.
我希望你修改它，我修改了很多很多它来定制它供我使用。如果你有资源，很多供应商都提供修复引擎Cameron和Swift。
I would prefer you modify it, I modified quite a lot of it to customize it for my use. If you have the resources there are lot of vendors who provide fix engines Cameron and Swift.
这篇关于是否值得将quickfixj从Mina迁移到Netty？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！