Broadcast Standards – Cloud Compute Infrastructure – Part 1
Once logged in you can set content preferences to let us know what you are interested in and whether you want to receive email from us.
Already Registered? Login
Welcome to Part 1 of Broadcast Standards – Cloud Compute Infrastructure. This collection of articles is the first in a new series which expands on the enormously popular ‘Broadcast Standards - The Book’ by Cliff Wootton. Over the coming months a series of Themed Content Collections will address specific aspects of the broadcast media supply chain from a standards-oriented perspective.
Part 1 contains three extended length articles which lay down the principles & terminology of cloud compute infrastructure, discuss the advantages of cloud compute systems, explores the various cloud compute architectural models, and describes the relationship between Kubernetes and the architecture it controls. It also tackles the core topic of timing and timing sources in cloud compute systems.
Related content:
About Broadcast Standards – Cloud Compute Infrastructure
Our first new Broadcast Standards theme explores the frequently mis-described concept of ‘cloud computing’, the microservices that run in this IT model, and some of the practical implications of deploying them within broadcast production infrastructure. Although the NMOS standards were devised to facilitate ST 2110 infrastructure they have also become central to the deployment of cloud compute infrastructure so they too are included in Part 2 of this series.
It is surprising but true that cloud computing is not based on ratified standards - it is based on open source and de-facto protocols and practices. It is however very well defined because the broadcast industry is leveraging IT technology that is widely deployed as part of the technology fabric on which society functions. These articles therefore describe the established protocols and practices that define cloud compute resource and how these relate to broadcast specific and other ratified standards.
‘Broadcast Standards – Cloud Compute’ will publish in three parts – details of all 3 Parts can be found HERE.
About Part 1.
Part 1 is a free PDF download which contains three, extended length original articles:
Article 1 : The Principles, Terminology & Structure Of Cloud Compute Based Systems
Here we outline the principles, advantages, and various deployment models for cloud compute infrastructure, along with the taxonomy of cloud compute service providers and the relevant regulatory frameworks.
Article 2 : Kubernetes & The Architecture Of Cloud Compute Based Systems
Here we describe Kubernetes and the taxonomy of containerized architecture based cloud compute system designs it manages.
Article 3 : Timing Systems In Cloud Compute Infrastructure
Timing domains & reference sources in cloud compute infrastructure and new non-linear timing infrastructure proposals.
Part of a series supported by
You might also like...
IP Monitoring & Diagnostics With Command Line Tools: Part 6 - Advanced Command Line Tools
We continue our series with some small code examples that will make your monitoring and diagnostic scripts more robust and reliable
Building Software Defined Infrastructure: Monitoring Microservices
Breaking production systems into individual microservice based processors, requires monitoring over IP via RESTful APIs and a database system to capture the results.
Monitoring & Compliance In Broadcast: Monitoring QoS & QoE To Power Monetization
Measuring Quality of Experience (QoE) as perceived by viewers has become critical for monetization both from targeted advertising and direct content consumption.
IP Monitoring & Diagnostics With Command Line Tools: Part 5 - Using Shell Scripts
Shell scripts enable you to edit your diagnostic and monitoring commands into a script file so they can be repeated without needing to type them manually every time. Shell scripts also offer some unique and powerful features that help to…
Building Software Defined Infrastructure: Observability In Microservice Architecture
Building dynamic microservices based infrastructure introduces the potential for variable latency which brings new monitoring challenges that require an understanding of observability.