Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
Dude...think about what you'r suggesting. You are implying that @NinjaTrader should have done something biased. We can't expect them to take a position against one of their partners, can we? We have to take responsibility for ourselves. personally, as a former IT professional I knew that if it wasn't resolved by Jan 1 night session that it wasn't going to be a quick fix. So I bailed on Mirus and moved my account. As of today I'm up and running at Optimus. I maintain that Ninja actually have done all and more than could be expected of them given their political position.
Yes I can deny that. It was a change in back end that caused the issue. API components did not cause the outage directly or indirectly. The API has no relevance on what has happened. I don't think I can be any clearer.
I work in IT as well, doing cloud services of all things.
And in my experience if stuff doesn't work because of a partner/supplier issue and you are not getting a good response you move your customers to an alternative service.
Your customer is happy you dealt with the problem.
You save face and do a good job for the customer.
The only people who lose out are the idiots who stuff it up for themselves in the first place.
Just to be technically clear and back up Ray here:
The API is the published public interface that supplies the "contract" between the service and the consumers of the service. The API should not be fundamentally tied to the layers below as the main function of good API's to abstract the actual layers below.
From my understand the Zenfire API has remained in place, but the layers/components providing the data and execution below it were completely changed (Rithimic / others to BigTick).
Also when I refer to API component I am not talking about an API specification I am talking about integrating a 3rd party codebase into your application which essentially runs as a black box inside your app.
Zenfire doesn't have their own service they just relabel someone else's service. So when they changed from Rithmic to BigTick that required changing the whole system.
Interestingly I was also a Cloud Service Provider but Ninja isn't. It wasn't Ninja's platform that failed. The infrastructure belongs to Mirus. Say you are hosting Microsoft Project Server for a client and your ISP's BGP goes south re-routing all your class "C"'s into outer space. From your customer's perspective it's your fault not the ISP and not Microsoft. You are the one providing an SLA on a service. It's up to you to either find a new ISP or work with the ISP to get the routing sorted out. Ninjatrader are like Microsoft in this instance. They are just the ISV.