Well that full maintenance fix lasted long...
Anybody remember back when there was really only one super active Vader reseller here, who charged for trials to repel the leeches off, didn't do stupid things such as pay youtubers like Soloman to do over-the-top reviews, and essentially contributed to a system where Vader wasn't being over-sold into the ground?
Good times. Vader really was great back then.
@Greencon10 - no the full service was not down - there was a misdeployment of a our backend api service that powers apk + website + kodi, which caused some authentication apis to not work - if you were logged, and watching the same category it would have worked fine. The outage lasted 30 min. Thats roughly the time it takes for our backend api to compile, transfer, and start up.
We routinely do deployments to the backend api, but because we migrated the servers to a new infrastructure the team is still getting used to it. Having said that your feedback is welcome and I hope this was a sufficient answer.
The outages, etc, has very little to do with Soloman, or extra load. The issue is xtream-codes is badly written, and poorly designed, We've had to engineer solutions around these limitations, and we've finally figured out the best possible solution.
If your interested we've basically deployed a galera cluster for the backend database, and gone with a kubernetes cluster for the backend api. We also moved to a completely virtualized enviornment (backed by bare metal) that allows for dynamic placement of the VMs' based on load, and demand.
Keep in mind the backend api for vaders is custom build by the vader team, hence you have our website, and our apk,etc, etc. That is all 100% our code, and tens of thousands of lines. There's no other provider out there that has invested the time, and money into actually building proper apis, backends, etc.
XC by default does not let you choose how you want to deploy your database, i.e) it only supports running your database on the same server that the XC api runs on - we had to hack our way around that as XC is a closed source software. We were able to successfully do it finally and the results so far are great. (I doubt anyone else using XC has even thought of doing this )
We added 2 weeks free to all users because we are fair - we tried to do maintenance for this migrations during off peak hours as doing these type of deployments on production environment cant take hours to days. We initially trie to do the migration a few days ago however, the new environment had a hard drive failure just as we finished, so we had to move it back to the old environment ( which was already strugling with the single DB instance )