3 ms·
"The main goal of the team was to implement a job processing pipeline that was vendor agnostic and cloud-based" I wonder if they feel they've achieved it? How m
by xchaotic 10y ago
"The main goal of the team was to implement a job processing pipeline that was vendor agnostic and cloud-based"
I wonder if they feel they've achieved it?
How much work would it be to switch away from their choice of JS libraries and AWS?
And if it's not trivial, what's the point?
- standel 10y agoIMO, they probably didn't want to be cloud vendor agnostic. They really wanted to be /video encoding/ vendor agnostic.
- xchaotic 10y agoDo you need 20 microservices for that? If you choose to swap a video vendor, I guess you need to write wrapper API calls for the new vendor? Even if the new vendor provides that out of the box, NYT amortizes those costs one way or the other...
- tveita 10y agoWhere do you see 20 microservices? I count a couple of video-specific ones, + some integrations with their existing systems.
- xchaotic 10y agoIt may be more or less, depending on how you count the, but what I'm really trying to figure out is whether the over engineering and the extra abstraction layers are justified in this case and in general. My experience so far is the opposite - Microservices, orchestration etc hide the complexity but don't remove it, so if the shit hits the fan, you still have to look under the hood and with Microservices, probably under 10 different hoods or a hood under the hood of a hood :)
- astrange 10y agoMultiple encoding vendors won't give you much. They're just different people writing different shell scripts that run ffmpeg (and not donating anything to the original project). I guessit lets you avoid a little price lock-in, but you could also just write your own shell script.
- elcct 10y agoThey could use something like Kubernetes and tools communicating with open standards