[This message was posted by Paul Raskin of RJ O'Brien <[email protected]> to the "General Q/A" discussion forum at http://fixprotocol.org/discuss/22. You can reply to it on-line at http://fixprotocol.org/discuss/read/86e87443 - PLEASE DO NOT REPLY BY MAIL.]
> I am curious how many folks out there configure their FIX engines to > save their logs to a relational database. Is this fairly common? I can > see advantages in terms of availability, but seems like it would be a > minus from a performance perspective. Relational database logging does offer a lot in terms of availability, failover/redundancy and reporting, but I wouldn't use it as a primary message store for the reason you mentioned, the performance hit. This does mean that you have to work out another scheme for persisting messages in such a way as to provide seamless failover, but this can be done in many ways that I would expect to be more efficient than using a relational database. Also, if you're logging to a database and it becomes inaccessible for some reason, you have no logging. One solution would be to do a hybrid implementation. For example, you could write messages immediately to a file or some in-memory cache, then lazily write them to a database. [You can unsubscribe from this discussion group by sending a message to mailto:[email protected]] -- You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/fix-protocol?hl=en.
