A new update to our automated infrastructure was applied.
In case of a hardware failure of any single cluster node, the failover time for switching to a backup node was reduced.
As the year is approaching its end, it is time to draw a short resume for 2019
A large share of the mixing service fee has always been dedicated to the investment into our server infrastructure.
Thanks to your contribution, we're able to provide and extend our global network of load balancers and broadcast servers.
The redundancy-by-design approach of FoxMixer results in a "no single point of failure" policy.
Next to maximizing ease of use, FoxMixer is coded from the ground with this principle in mind - and it has not been added as an afterthought!
It can't.
From our experience with cluster management, multi-node systems which are bended to failure tolerance as an afterthought are doomed to fail.
Thinking about critical design questions and rare corner-cases beforehand is time consuming and sometimes straining, but has payed off for our team at every step we have taken.
This has allowed us to deliver the high-quality service and uptime that FoxMixer is providing.
And still, we're maintaining all of this with all log features turned off. We don't delete logs. Because we don't even generate them.
The mixing engine itself has always been highly fault-tolerant.
And now, our infrastructure is becoming more and more automated as well. To such an extend that it can cope automatically with all kinds of events that may occur.
We're proud to announce that there has been no downtime due to hardware or software failures during the entire year at all, even though the amount of mixing requests has increased.
All mixes were payed out in time. All of them.
Our team doesn't want to miss out the opportunity to say thank you to all our new users that are trusting us with their large amounts of coins
and we highly value the users who have been following us along the way since our start back in 2017!
Keep your privacy
And have a good mix!
In case of a hardware failure of any single cluster node, the failover time for switching to a backup node was reduced.
As the year is approaching its end, it is time to draw a short resume for 2019
A large share of the mixing service fee has always been dedicated to the investment into our server infrastructure.
Thanks to your contribution, we're able to provide and extend our global network of load balancers and broadcast servers.
The redundancy-by-design approach of FoxMixer results in a "no single point of failure" policy.
Next to maximizing ease of use, FoxMixer is coded from the ground with this principle in mind - and it has not been added as an afterthought!
It can't.
From our experience with cluster management, multi-node systems which are bended to failure tolerance as an afterthought are doomed to fail.
Thinking about critical design questions and rare corner-cases beforehand is time consuming and sometimes straining, but has payed off for our team at every step we have taken.
This has allowed us to deliver the high-quality service and uptime that FoxMixer is providing.
And still, we're maintaining all of this with all log features turned off. We don't delete logs. Because we don't even generate them.
The mixing engine itself has always been highly fault-tolerant.
And now, our infrastructure is becoming more and more automated as well. To such an extend that it can cope automatically with all kinds of events that may occur.
We're proud to announce that there has been no downtime due to hardware or software failures during the entire year at all, even though the amount of mixing requests has increased.
All mixes were payed out in time. All of them.
Our team doesn't want to miss out the opportunity to say thank you to all our new users that are trusting us with their large amounts of coins
and we highly value the users who have been following us along the way since our start back in 2017!
Keep your privacy
And have a good mix!