How we helped our client Save & Stabilize their business?
How we helped our client Save & Stabilize their business?
Overview
Our client is a leader in the online binary options industry renowned for having the fastest payout processing times and for providing first class customer service one can trust.
Our client is a leader in the online binary options industry renowned for having the fastest payout processing times and for providing first class customer service one can trust.
Unsatisfied with the existing service provider and they decided to partner with us to maintain their binary options trading application for better services at lesser costs.
We provided them with an end to end solution including web development, application development, code labeling, database, and server maintenance.
With more than 2 millions users globally there is no margin for errors.
The users should have the liberty to select a personalized web address, pick themes and templates of their choice.
Challenges
We received the handover from the previous service provider with only a high level diagram of the network. There were no in depth information on the server network structure, the location of the servers and their numbers.
The objective was to keep the application devoid of any game lag which could hurt the business.
Soon after the project begun, the client confirmed that the binary data was not flowing into the application system. To fix the issue, we tried to restart the services using Jenkins which is the automation software used for continuous integration of every coding deployment on the website.
However, much to our surprise, we found that the automation software files were not present and no backup file could be found in the Docker content to run Jenkins. It happened due to damage to the physical server.
Implementation of Plan
As a solution to handle the project, we advised the client to hire a dedicated team of project managers and developers. With this model, cost of hiring for the client was reduced to half. Due to the failure, the client was facing extreme pressure from the users end. We had very little information on what were the services defined in Jenkins and without this information it was not possible to resume the data flow back into the application. This was a serious threat.