Building Software Defined Infrastructure: Part 1 - System Topologies
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 Building Software Defined Infrastructure - a new multi-part content collection from Tony Orme. This series is for broadcast engineering & IT teams seeking to deepen their technical understanding of the microservices based IT technologies that are set to drive the next phase of transition from hardware to software based broadcast systems.
Part 1 contains four articles which discuss what Software Defined Infrastructure is, the infrastructure models it enables, how virtualization and microservices differ, how microservices form the basis of Software Defined Infrastructure and why they provide much better solutions for broadcasters, especially when considering scalability, resilience and security.
About Building Software Defined Infrastructure
As an industry, we’ve now ticked box one of “how to build IP infrastructures” by reliably streaming video, audio and metadata over enterprise IP networks. Now, we need to greatly simplify IP broadcast infrastructures to improve their operation and integration.
This series seeks to clarify what is meant by Software Defined Infrastructure, how its fundamental design philosophy is key to the next evolutionary step for broadcast systems, and how it can benefit broadcasters with scalability, reliability, resilience and very high levels of security.
We discuss the fundamental differences between virtualization and microservices and how microservice based systems go hand in hand with Software Defined Networks in the design and implementation of truly scalable systems.
The next phase of our IP enabled journey is going to be one of delivering simplicity and integration through microservices. For IP to become the success it promises, we need to look more closely at how we make it work operationally so that simplicity and integration become as easy as maintaining a high-quality internet mobile phone connection when walking from the office to the park.
Building Software Defined Infrastructure will publish in 4 parts. Details of all four parts can be found HERE.
About Part 1 – System Topologies
Part 1 is a free PDF download which contains four original articles:
Article 1 : What Is Software Defined Infrastructure?
What Software Defined Infrastructure is, what infrastructure models it enables and a discussion of on- and off-prem cloud infrastructure.
Article 2 : Virtualization Vs Microservices
How virtualization and microservices differ, and workflows where virtualization and microservices would be used or avoided in terms of reliability, flexibility and security.
Article 3 : Virtualizing Idle Time
Our partner Lawo discuss why “software-defined” as an approach should be considered a prerequisite in any forward-looking, IP-based broadcast environment.
Article 4 : Software Defined Infrastructure Components
How microservices form the basis of Software Defined Infrastructure and why they provide much better solutions for broadcasters, especially when considering scalability, resilience and security.
Part of a series supported by
You might also like...
IP Security For Broadcasters: Part 11 - EBU R143 Security Recommendations
EBU R143 formalizes security practices for both broadcasters and vendors. This comprehensive list should be at the forefront of every broadcaster’s and vendor’s thoughts when designing and implementing IP media facilities.
Live Sports Production: The Rise Of Remote Hybrid Workflows
A discussion of the rise of remote production, why OB workflows remain first choice in tier one production and the emergence of new hybrid workflows.
Building Software Defined Infrastructure: Software Defined Infrastructure Components
There is much more involved in deploying effective microservices than just designing small footprint software applications. In this article we look at containers, why we need them, and the components needed to make the infrastructure work effectively.
IP Security For Broadcasters: Part 10 - NATS Advanced Messaging
As IT and broadcast infrastructures become ever more complex, the need to securely exchange data is becoming more challenging. NATS messaging is designed to simplify collaboration between often diverse software applications.
Standards: Part 26 - An Introduction To Metadata
Here we describe how metadata facilitates your asset workflow and distribution. It keeps track of your products in the archives so they can be re-purposed and monetized later.