Service Oriented Architecture
Sep 1, 2007 12:00 PM
SOA is the new way to design a facility’s workflow.
The broadcast industry has a great need for agility and efficiency in dealing with new technologies and business models. Distributing content to HDTVs, mobile phones and software-based media appliances imposes new challenges on the production workflows of all media enterprises.
Advances in technology are moving so rapidly that media companies can no longer add or change a system without considering how quickly it will become obsolete. Although file-based production allows for less expensive, faster turn-around, it also introduces new issues such as security, administration and media management, all of which must be dealt with efficiently. Large, single-vendor, vertically integrated solutions with a long ROI are quickly becoming impractical.
Media companies have traditionally integrated each new system or business model separately. Getting one new system online in a media enterprise can be relatively straightforward. A new HD editing system, for example, can usually be installed and configured relatively easily. Connecting it to other systems in the enterprise (such as automation or asset management) was likely part of its selection process, so integrating it in the workflow is largely an exercise in vendor management.
A patchwork approach to integrating each new system and business model, however, really doesn’t work in the digital age. (See Figure 1 on page 66.) Even with good system-design practices, this course of action will create further hurdles over time. After two, three, 10 or 20 such additions, a media enterprise is left with multiple silos of vertically integrated systems working together over tenuous communication channels. This kind of tightly-coupled, point-to-point architecture inevitably relies on informal data (phone calls, e-mails, etc.) to communicate important production-chain information (such as tape numbers or clip metadata). Data can be easily lost, misunderstood or entered with errors into multiple systems. Each subsequent change becomes more difficult than the previous because each system iteration adds complexity.
The real challenge today is not to address each individual change, but the process itself of making these changes. In short, broadcast companies need to build business agility into their design process and infrastructure so that when faced with new distribution models or content-production requirements, they are able to react efficiently and effectively. In the digital age, this has become essential to broadcasters and media facilities. A technology solution known as Service Oriented Architecture (SOA) is one way to do this.
Understanding SOA
A system architecture that addresses the business needs faced by broadcasters today must:
- Facilitate the development of highly reusable business and infrastructure components.
- Have an easy-to-implement alteration and update strategy for these components.
- Allow for the greatest transparency of standards and other communications options among these components.
Figure 1
A focus on reusability and ease of alteration allows such a system to address both current and future business requirements. (See Figure 2 on page 68.) SOA is such an approach; it treats discrete and reusable business functions as services because they offer a business service to the rest of the enterprise. Instead of concentrating on points of integration and technical compatibility, SOA operates according to a functionality-centric facility design. Beginning with the traditional tightly coupled verticals of software, an integrator can design and connect reusable services using SOA technologies.
Even though most software vendors (including producers of software-based media systems) do not currently claim SOA support, their software can be made compliant to a facility’s SOA by wrapping the programmatic interfaces offered by the software to a service interface. (See Figure 3 on page 70.) This creates reusability because vendors that offer different implementations — but essentially the same business service — can be individually wrapped to present the same service interface. A service interface is the only communication point between that software and the rest of the media facility in an SOA, so it presents a single point for alteration. If the underlying application changes, only the connections between that consistent wrapper and the specifics of a vendor’s API need to be changed. This is known as separating interface from implementation.
Figure 2
The way an SOA addresses greater transparency is through the use of a common messaging “layer” built over an enterprise network. This middleware layer provides the communication infrastructure needed for various services to interoperate. It is a single network, which means that there is a common location for data management, information gathering and security. However, it can also be distributed over many computers or many facilities, providing necessary redundancy and reliability.
Once several services are connected to the middleware layer, the benefits of SOA begin to really become apparent. Some of the best practices of Business Process Management (BPM) can be put in place in the form of automated business processes that work in the middleware layer and orchestrate communication among services.
Depending on how it’s defined, SOA has been around for a decade or more; it is not a new concept. The media industry is one of last verticals to begin adopting SOA extensively throughout its business. SOA has been put to use successfully in many other industries, including manufacturing, banking, retail, healthcare and telecom. Billions of dollars a day move through an SOA middleware layer. In fact, in heavily regulated industries (such as healthcare or finance), the use of defined services helps companies meet stringent privacy and security requirements. It also helps ensure that new business models and technologies fall within regulation.
| Want to use this article? Click here for options! |  |
