From: Colin D. <co...@ma...> - 2022-04-18 16:48:09
|
I don't have experience with Azure, but we did migrate a co-hosted installation from NY3 to GCP to save costs. We used Google's special fiber interconnect, the name of which escaped me. It worked fine except that we had to get Google engineers to physically clean one of the fiber connections before we stopped experiencing flaps. That's probably beside the point. It worked fine with an expected and tolerated increase of latency. More and more of our installations are cloud-based. We don't try to compete in the microsecond space, so, it doesn't really matter to our clients and saves a lot of money. On 4/18/22 04:56, Robert Nicholson wrote: > QFJ Documentation: http://www.quickfixj.org/documentation/ > QFJ Support: http://www.quickfixj.org/support/ > > > What have been people’s experiences migrating QuickfixJ FIX clients to cloud platforms? In particular Azure. > > Have you found that you still kept your FIX clients on prem and delivered the FIX payload to the cloud or did you go the full hog and host your FIX client in the cloud using an Express route back thru your firms datacenter to route to your FIX end points? > > I can think of using AMQP senders off prem to event hubs / service bus in the cloud as one approach to getting FIX payload into a pipeline hosted in the cloud. > > > > _______________________________________________ > Quickfixj-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfixj-users -- Colin DuPlantis Chief Architect, Marketcetera Download, Run, Trade https://www.marketcetera.com |