Services Oriented Architecture at NOS

Service Oriented Architecture PHP Benelux March 4th 2010

About me

This is what I am

Especially for @skoop i wanted to talk about FC Twente but i will leave that untill next time :-)

New Media department ‣ 1 head of New Media ‣ 4 developers (including myself) ‣ 2 designers ‣ 2 projectmanagers ‣ 1 freelance interaction designer always, everywhere ‣ 1 freelancer designer for everybody ‣ 5 freelance developers ‣ 1 freelancer prijectmanager 17

Growing amount of different parties and platforms is a problem challenge

Our solution for the growing amount of platforms is the central content database

Architecture overview Back-End Content Platform Narrow Website Mobile Syndication Casting

Content Platform is the heart ‣ All external publication of content comes from the content platform ‣ The website, mobile website etc.. are all generated by this platform ‣ Every content item has the same basic set of meta-data ‣ Content database holds all information about articles, files, video, audio, broadcast, live events, live scores etc..

Content Platform Architecture Write actions Master Database Master Database Content Platform Read actions SQL Proxy Slave 1 Slave 2 Slave 3 Slave 4

Content Platform Modules ‣ Admin (just to manage accounts and log files) ‣ Import routines (import of content from different resources) ‣ Export routines (creates RSS Feeds, special XML feeds for partners) ‣ API (for internal and external use) ‣ Social (connections to Twitter and other social networking systems)

More than 1 system ‣ The whole New Media part of NOS is setup as a SOA enviroment ‣ This means we run a lot of different pieces of software (almost everything is developed our selfs) ‣ All system talk to each other on XML basis (an yes, that’s human readable XML)

Example a news story

Example, a news story on the website

Architecture Dataﬂow Systems Small Story on Cyclone Teletekst XML XML Content Tridion CMS Management XML XML Content PHP + MySQL Database XML XML HTML + JS + Website PHP + MySQL

Disadvantages ‣ 4 different systems are involved that have to be maintained ‣ More sytems and connections means a bigger chance of failure (but we solved that with monitoring systems)

Advantages of this way ‣ The 4 systems are very good at their own job ‣ Each system is proven technology ‣ Connections are XML based, it’s all human readable XML ‣ Each system can be replaced with another system if it outputs (or imports) the same XML

How we implemented Search at our website

65.000 articles, 40.000 video’s, 50.000 audio clips

Search Architecture Content Website Database API SOLR Engine Index

Loosely coupeled ‣ Use of proven technology (we use a SOLR search engine) ‣ Easy to maintain ‣ Open system, build on the future ‣ XML, PHP, JSON in- and export ‣ Stupid engine, garbage in = garbage out ‣ API makes it easier to connect

Search engine is used not only to search

Result page of the search engine

Example, broadcasts on the website Another example, the search engine

Architecture Direction Studio Television Cable Companies Broadcast XML Triggers Encoder 2 Encoder 1 XML and video ﬁle XML and video ﬁle Content Database

How this works ‣ Every (almost) broadcast we do is live ‣ When the studio signals is going to the public channel a trigger is send to the encoders (XML trigger) ‣ The encoder starts because it receives a trigger ‣ After the broadcast is finished another trigger (XML) is send, the encoder stops ‣ The encoders put’s the encoded files on the file system

How this works ‣ The encoded files are received by a content listener (some sort of service) ‣ The content listener put’s the files on the correct systems and tells the content databases about the existence of the file ‣ Meta-data is generated automatically ‣ The files are published to the website

Result ‣ You can watch the broadcast anywhere at anytime on a lot of devices ‣ Internet (website) ‣ Mobile (website and application) ‣ Philips NetTV ‣ Sony Bravia TV ‣ Sony Playstation ‣ and more....

Last weeks:-)

Vancouver Olympics 2010

Results (16 days) ‣ 2,7 million unique visitors ‣ 38+ million pageviews ‣ 4,5 million started LIVE streams ‣ 9 million starten on-demand streams ‣ Most viewed video is the crash of Koemaritasjvili

SOA Elements in this website ‣ Live-streaming is done with a player that use a webservice to redirecting views to the correct stream ‣ Schedule is updated from a external source (webservice) every 30 minutes ‣ News, Video, Audio and other material comes from the internal API of the content database ‣ Uses our internal search-engine (see before in the presenation)

Questions?

@jweshuis http://twitter.com/jweshuis http://www.janwillemeshuis.nl

http://janwillemeshuis.nl	55
http://app-enterprise02.dyndns.biz	9
http://www.slideshare.net	1

Services Oriented Architecture at NOS

by Jan Willem Eshuis on Feb 21, 2010

Accessibility

Categories

Tags

Upload Details

Usage Rights

3 Embeds 65

Statistics

Services Oriented Architecture at NOS — Presentation Transcript