The Encoding Gateway Has Officially Retired

As most of you who follow this blog know, Tibs and I have spent the past month transitioning @threespeak into a new era. Most of the heavy lifting is done, but there were still a few final bricks left to lay.

Well, today those bricks were finally laid.

In an effort to survive this relentless bear market, we've retired two more servers from the @threespeak infrastructure. Naturally, that meant moving things around, but it also gave us the opportunity to completely abandon the old upload and publishing pipeline.

The infamous encoding gateway—the piece of software that somehow survived countless iterations over the years—has officially been retired. The server that hosted it is gone, and with it, a lot of unnecessary complexity. The entire system has been simplified considerably, which I consider a huge win.

The biggest advantage is that the new upload and embed system scales much more easily. If things suddenly turn around tomorrow and we see a surge of users, we can spin up additional ingest servers relatively quickly and distribute the load. That simply wasn't practical with the old architecture.

For regular ThreeSpeak users, this transition has already happened. If you've uploaded videos over the past few weeks, you've hopefully noticed the improvements. However, if you're running an Encoding Node, you'll need to pull the latest changes from Git and rebuild.

During the transition, encoding nodes had to support both the old and new systems simultaneously, polling two different paths and juggling two workflows. Thankfully, that's no longer necessary. The new system eliminates the need for forced videos, manual corrections, and Rescue Mode altogether—a change I'm very happy to see.

So that's the PSA.

If you operate an Encoding Node, don't forget to update and redeploy.

— MenO