Emanuele Bartolesi will present on Real Solutions Day about Azure Media Services and Azure Search. He will demonstrate how to use Azure Media Services to encode, package and stream video and audio files. He will also demonstrate how to use Azure Search to build a search index and query data. The agenda includes overviews of Azure Media Services and Azure Search, followed by demonstrations of each service.

1. Real Solutions Day
Emanuele Bartolesi – MVP ASP.NET
CEO & Founder SmartCore Tech
Media Services &
Azure Search

2. Ringraziamenti
In collaborazione con
Con la sponsorizzazione di
15/12/2014#RealSolutions - Real Solutions Day

3. Who I Am
15/12/2014#RealSolutions - Real Solutions Day
Emanuele Bartolesi
 Microsoft MVP ASP.NET
 Founder of SmartCore Tech
 DotNetToscana Staff Member & Speaker
 Speaker for various events
 Trainer
 SharePoint addicted from 2007
 Enthusiast ASP.NET Developer
 NopCommerce Contributor
 MCPD Web applications, MCTS BING Applications, MCTS
Silverlight, MCTS HTML5 & CSS3
 Italian blog: www.emanuelebartolesi.com
 English blog: www.emanuelebartolesi.com/en
 Twitter: @kasuken
 Email: emanueleb@outlook.com

4. Agenda
 Azure Media Services
 Demo
 Azure Search
 Demo
15/12/2014#RealSolutions - Real Solutions Day

5. Azure Media Services
Real Solutions Day
15/12/2014

6. Overview
 NetFlix produces 33% of the world's Internet traffic (from
21:00 to 24:00)
 40% of internet traffic is video (today), growing to 80%
(2015)
 50 million internet connected TV sold this year
 150 million video capable smartphone (and counting)
 200 million consoles sold this year
15/12/2014#RealSolutions - Real Solutions Day

7. http://.../
Smartphone
Tablet Computer
Laptop
15/12/2014#RealSolutions - Real Solutions Day

8. Video Encoding [input formats]
• 3GPP
• 3GPP2
• ASF
• AVI
• DV
• MOD
• M2TS
• MP4
• MPEG-1
• MPEG-2
• MTS
• PIFF 1.3
• TS
• VOB
• WMV
• XESC
Input
formats
(containers)
• DV
• H.264
• MPEG-1
• MPEG-2
• MPEG-4 v2
• VC-1
• WMV
Input
codecs
15/12/2014#RealSolutions - Real Solutions Day

9. Video Encoding [output formats]
Output
formats
(containers)
• MP4
• PIFF 1.1
• WMV
• H.264
• VC-1
Output
codecs
Streaming
formats
• HLS
• Smooth Streaming
• MPEG DASH
15/12/2014#RealSolutions - Real Solutions Day

10. Audio Encoding [input & output]
• AC3
• AIFF
• BWF
• MP3
• M4A
• M4B
• WAV
• WMA
Input
formats
(containers)
• AC-3
• AAC
• AAC-LC
• HE-AAC v1
• HE-AAC v2
• MP3
• WMA
Input
codecs
Output
formats
(containers)
• AAC
• WMA
• AAC-LC
• HE-AAC v1
• HE-AAC v2
• WMAOutput
codecs
15/12/2014#RealSolutions - Real Solutions Day

11. Resources Workflow
…
Input media files
Asset
…
Output media files
Asset:
• Contains digital files (video, audio, text tracks, etc.)
• Contains metadata about digital files
• Mapped to Azure Blob Storage
Blob
15/12/2014#RealSolutions - Real Solutions Day

12. Resources Workflow
Asset
Task:
• Contains asset processing instructions
Processor:
• Compute resource to be used for work
Encode EncryptThumbnails Package
Tasks
Processor Processor Processor Processor
15/12/2014#RealSolutions - Real Solutions Day

13. Resources Workflow
Asset
Job:
• Combines several tasks
• Contains details of the processing work
• Event handling
• Monitoring
Job
Progress EventsTask execution
15/12/2014#RealSolutions - Real Solutions Day

14. Media Services – First look
Real Solutions Day
15/12/2014
1
2
3

15. Media Services – First demo
Real Solutions Day
1
2
3

16. Q&A
Real Solutions Day

17. Azure Search
Real Solutions Day

18. Agenda
 What is Azure Search
 Why Azure Search
 How it works
 Limitations
 Types
 Search operators
 Demo
15/12/2014#RealSolutions - Real Solutions Day

19. What is Azure Search
 Full-text engine
 Platform as a service (Paas)
 Admin by Rest API
 Data exchange with JSON
15/12/2014#RealSolutions - Real Solutions Day

20. Why Azure Search
15/12/2014#RealSolutions - Real Solutions Day

21. How it works
 Create the Azure Search Service
 Get the admin and search key
 Create the index
 Upload documents
 Query the index
 Maintain the index
15/12/2014#RealSolutions - Real Solutions Day

22. Limitations - free
Object Limit
Maximum number of indexes 3
Maximum document count 10,000
Maximum storage size 50 MB
Maximum partitions N/A
Maximum replicas N/A
Maximum search units N/A
15/12/2014#RealSolutions - Real Solutions Day

23. Limitations - standard
Object Limit
Maximum number of indexes 50 per Search service
Maximum document count 15 million per partition
Maximum storage size 25 GB per partition
Maximum partitions 12 per Search service
Maximum replicas 6 per Search service
Maximum search units 36 per Search service
15/12/2014#RealSolutions - Real Solutions Day

24. Limitations – Request Sizes
 Maximum of 16 MB per request
 Maximum 8 KB URL length
 Maximum 1000 documents per batch of index uploads,
merges, or deletes
 Maximum 25 characters of text in Suggest API request,
minimum 3 characters
 Maximum 32 fields in $orderby clause
 Maximum search term size is 32766 bytes (32 KB minute 2
bytes) of UTF-8 encoded text
15/12/2014#RealSolutions - Real Solutions Day

25. Types
Edm.String
Text that can optionally be tokenized for full-text search (word-breaking,
stemming, etc.)
Collection(Edm.String) A list of strings that can optionally be tokenized for full-text search.
Edm.Boolean Contains true/false values.
Edm.Int32 Integral numeric data.
Edm.Double Double-precision numeric data
Edm.DateTimeOffset
Contains a date and time as an offset in minutes from GMT. In the OData V4
format: "yyyy-mm-ddTHH:mm:ss.fffZ". Azure Search requires all date/time values
are required to be in UTC (indicated by the 'Z' suffix).
Edm.GeographyPoint
A point representing a geographic location on the globe. For request and
response bodies the representation of values of this type follows the GeoJSON
"Point" type format. For URLs OData uses a literal form based on the WKT
standard. A point literal is constructed as geography'POINT(lon lat)'.
Edm.GeographyPolygon
A polygon representing a geographic region on the globe. While this type
cannot be used in document fields, it can be used as an argument to the
geo.intersects function. The literal form for URLs in OData is based on the WKT
standard. A polygon literal is constructed as geography'POLYGON((lon lat, lon
lat, ...))'. NOTE: points in a polygon must be in counterclockwise order.
15/12/2014#RealSolutions - Real Solutions Day

26. Operators
+
AND operator. For example, wifi+luxury will search for documents containing both "wifi" and
"luxury"
|
OR operator. For example, wifi|luxury will search for documents containing either "wifi" or "luxury"
or both
-
NOT operator. For example, wifi -luxury will search for documents that have the "wifi" term and/or
do not have "luxury" (and/or is controlled by searchMode)
*
Suffix operator. For example, lux* will search for documents that have a term that starts with "lux",
ignoring case.
"
Phrase search operator. For example, while Roach Motel would search for documents containing
Roach and/or Motel anywhere in any order, "Roach Motel" will only match documents that
contains that whole phrase together and in that order (text analysis still applies).
( )
Precedence operator. For example, motel+(wifi|luxury) will search for documents containing the
"motel" term and either "wifi" or "luxury" (or both).
15/12/2014#RealSolutions - Real Solutions Day

27. What’s New
 Current API version is 2014-10-20-Preview
 27 languages - http://msdn.microsoft.com/en-us/library/azure/dn879793.aspx
 New Regions: North Cetral US & South Central US
 Azure Portal Index Creation & Management
15/12/2014#RealSolutions - Real Solutions Day

28. Azure Search – First look
Real Solutions Day
1
2
3

29. Q&A
Real Solutions Day