A package manager for a software stack the does not change that often (a) can move managed services like databases, message queues or even more complex obseravbility tools inside the cluster with the same convenience of a manage service.
If your setup become more complex and changes often (b) a I would recommend breaking it up into smaller pieces.
For both scenarios it makes sense to use git to keep track of revision and previous states of your Kubernetes cluster and incorporate review processes with pull requests.
While we have CMAF and CENC as standards, politics of companies like Apple just decide to change the cipher mode on DRM for HLS Fairplay and suddenly it's a problem for the whole industry.
Oh, totally agree, just because we can stream and display the content in HDR, it doesn't mean that the production was really worth it. However, content quality in HDR just increases every day, there is so much competition for great content right now that we will just see more great things. Even normal user generated content can now be created with the iphone and dolby vision, which is really crazy and cool. I think we are just at the beginning, maybe HDR will be the standard in a few years from now
Depends on what you classify as relevant targets. All big hardware companies have been onboard since the begging and probably already have prototypes of fixed-function decoders. Chances are we'll have consumer hardware with such decoders sometime next year.
If you actually go on the AV1 spec issue tracker, there are issues (both closed and open) from people at Nvidia, ARM's hardware team, Google and Netflix.
Now that I have your ear, may I make a suggestion? Please be a little more specific about what Bitmovin does on your website. Right now the first thing I read is:
"Software to Solve Complex Video Problems.
Bitmovin API based products help developers around the world
solve the most complex video problems with cloud native software that runs anywhere"
That is a very broad statement. I would consider myself quite technical but I don't have deep domain knowledge in video coding and infrastructure. Quite honestly I can't get much information out of this.
What kind video problems are you solving (except that they're "most complex")? What is "cloud native software"? How do you define "runs anywhere"? Will it run on my Smartphone / PC / Car / Container / Toaster?
- serving videos for different screen size(if you send same video to all device, device has to do resizing in addition to decoding)
- serving videos in different network conditions(HLS/DASH) where based on bandwidth lower/higher bitrate video is requested from the server.
- seamlessly serving videos by switching video sources even for encrypted content.
- In HLS/DASH, player is the complex(intelligent) part as it senses the bandwith and send requests to server, they are giving readymade player implementation through SDK's
For us it was really important to find people that help us along the way, and that definitely includes all our investors, as well as Ycombinator. We're engineers and we definitely learned so much about building a product and a go to market strategy during our time at YCombinator. Having a technology alone is often not enough.
We also raised money form some silicon valley veterans and angels, and I use them as a resource for advice and expertise. One of the was the first CTO of Cisco for example, and I always learn so much in talking with him. Pretty cool to see how one can apply things from those companies also today.
But most importantly, it's the team. you need a great to come to this point, otherwise you struggle quite early. I'm really proud to work with our folks, they really do all the work.
a.) in Kubernetes setups that operate the same software stack, with the ongoing updates and regular releases.
b.) in Kubernetes setups that frequently install new software/diverse software