Hi! Welcome to This Is My Architecture
I am Woody from AWS and this is Emanuele from De Agostini Editore
- Hi, Woody. - Hi, Emanuele.
Welcome, tell us what De Agostini does.
De Agostini was founded in 1901
it's active in publishing industry
and media industry.
For the media part, in particular
Digital De Agostini was created 10 years ago
to manage tv channels,
websites and mobile apps,
where we distribute millions of stream views per month.
Do you do video on-demand? live?
Both.
- Both live and on demand. - Interesting.
What are you going to talk about today?
Today I will tell you
about our distribution architecture,
our video platform,
which is divided in two workflows,
one for contents upload,
and the other one for distribution.
Tell us how it works.
It all starts when an author
from their device
decides to upload multimedia content.
They access a centralized platform
running on EC2,
and uploads content and related metadata
that, once processed by EC2 instance,
go to a bucket,
S3.
Object storage, then.
Extactly.
Then, coordinated by a Lambda function,
the first Step Function starts,
which we call process function,
which validates multimedia content
uploaded on the S3 bucket,
and more importantly creates
through Elastic Transcoder,
creates project settings profiles,
typically
low, medium and high quality.
Different formats for different clients.
- Exactly. - OK.
Another important processing step
uses Transcribe
for speech-to-text
of the multimedia content
to enrich metadata
of this content.
Transcribing the audio of the videos
to index them.
Exactly, we enrich the content
and use this text
to enhance content positioning
on search engines, for example.
The other part of the architecture?
The last Step Function
which starts here,
again coordinated by a Lambda,
publishes the content
which is moved from S3
to S3 again
but in a final destination bucket
and propagated to our CDN.
Cloudfront.
This for the video on-demand part.
Correct?
This for the video on-demand part.
We were talking about streaming live, too.
Exactly.
We can distribute to our users
live events and contents
We do it by taking the signal
from our television broadcasting
in M3U8 format
bringing this signal
to our CDN
and broadcasting it to the thousands
of users connected to our CDN.
What are the advantages of this kind of architecture?
The advantages are certainly
the infrastructure management,
as the distribution part is serverless,
which simplifies the operation
and a high level user experience
thanks to
AWS managed services.
Thanks to the scalability of the services used?
Exactly.
Are you planning any evolution
of this architecture?
Yes, two at least.
A first need is
to integrate, use the API Gateway
and integrate
the company CMS,
we use to manage the sites
and the app backends
so we use API Gateway.
A second evolution
could be the use
the output of Transcribe
which enriches the metadata
to provide more personalized services
and give more relevant suggestions to our users
when they use the contents.
Services such as Comprehend
to give relevant suggestions based on texts
extracted by Transcribe, correct?
Exactly, this is the purpose.
Perfect. Thanks, Emanuele.
Very kind of you, and very interesting.
And thank you all for watching This Is My Architecture